我正在尝试找出一种方法来加速特别麻烦的查询,该查询按日期将数据汇总到几个表中。完整的(丑陋的)查询与下面的一起EXPLAIN ANALYZE显示了它的可怕程度。
EXPLAIN ANALYZE
如果有人可以窥视一下,看看他们是否可以发现任何很棒的重大问题(这很可能,我不是Postgres家伙)。
因此,这里去。查询是:
SELECT to_char(p.period, 'DD/MM/YY') as period, coalesce(o.value, 0) AS outbound, coalesce(i.value, 0) AS inbound FROM ( SELECT date '2009-10-01' + s.day AS period FROM generate_series(0, date '2009-10-31' - date '2009-10-01') AS s(day) ) AS p LEFT OUTER JOIN( SELECT SUM(b.body_size) AS value, b.body_time::date AS period FROM body AS b LEFT JOIN envelope e ON e.message_id = b.message_id WHERE e.envelope_command = 1 AND b.body_time BETWEEN '2009-10-01' AND (date '2009-10-31' + INTERVAL '1 DAY') GROUP BY period ORDER BY period ) AS o ON p.period = o.period LEFT OUTER JOIN( SELECT SUM(b.body_size) AS value, b.body_time::date AS period FROM body AS b LEFT JOIN envelope e ON e.message_id = b.message_id WHERE e.envelope_command = 2 AND b.body_time BETWEEN '2009-10-01' AND (date '2009-10-31' + INTERVAL '1 DAY') GROUP BY period ORDER BY period ) AS i ON p.period = i.period
将EXPLAIN ANALYZE可以在这里找到:在explain.depesz.com
任何意见或问题表示赞赏。
干杯
在Craig Young的建议的基础上,这是经过修改的查询,它对我正在处理的数据集运行约1.8秒。这与原始的〜2.0s相比有一点改进,而与Craig’s的〜22s相比有很大的改进。
SELECT p.period, /* The pivot technique... */ SUM(CASE envelope_command WHEN 1 THEN body_size ELSE 0 END) AS Outbound, SUM(CASE envelope_command WHEN 2 THEN body_size ELSE 0 END) AS Inbound FROM ( /* Get days range */ SELECT date '2009-10-01' + day AS period FROM generate_series(0, date '2009-10-31' - date '2009-10-01') AS day ) p /* Join message information */ LEFT OUTER JOIN ( SELECT b.body_size, b.body_time::date, e.envelope_command FROM body AS b INNER JOIN envelope e ON e.message_id = b.message_id WHERE e.envelope_command IN (2, 1) AND b.body_time::date BETWEEN (date '2009-10-01') AND (date '2009-10-31') ) d ON d.body_time = p.period GROUP BY p.period ORDER BY p.period