explain.depesz.com

A tool for finding a real cause for slow queries.

Result: iXP

options
Did it help? Consider supporting us - Bitcoin address: 12v2hUztAk2LgzQ9H9LMwuU32urHMjZQnq
# exclusive inclusive rows x rows loops node
1. 114.140 1352.654 ↓ 1840.3 42326 1

Nested Loop (cost=15852.83..34734.43 rows=23 width=52) (actual time=154.143..1352.654 rows=42326 loops=1)

  • Join Filter: ((max(auditor_sums.anchor_date)) = as_end.anchor_date)
2. 89.138 857.580 ↓ 105.6 42326 1

Nested Loop (cost=15852.83..30547.88 rows=401 width=36) (actual time=154.127..857.580 rows=42326 loops=1)

  • Join Filter: (as_start.anchor_date = (min(auditor_sums.anchor_date)))
3. 56.654 175.878 ↓ 5.6 42326 1

HashAggregate (cost=15852.83..15927.94 rows=7511 width=8) (actual time=154.094..175.878 rows=42326 loops=1)

4. 119.224 119.224 ↑ 1.0 79321 1

Seq Scan on auditor_sums (cost=0.00..15251.48 rows=80181 width=8) (actual time=79.604..119.224 rows=79321 loops=1)

  • Filter: ((anchor_date >= '2012-01-01'::date) AND (anchor_date <= '2012-02-01 00:00:00'::timestamp without time zone))
5. 592.564 592.564 ↑ 1.0 11 42326

Index Scan using "IX_auditor_sums_contract_id_fkey_auditor_sums" on auditor_sums as_start (cost=0.00..1.77 rows=11 width=32) (actual time=0.005..0.014 rows=11 loops=42326)

  • Index Cond: (contract_id = auditor_sums.contract_id)
6. 380.934 380.934 ↑ 1.0 11 42326

Index Scan using "IX_auditor_sums_contract_id_fkey_auditor_sums" on auditor_sums as_end (cost=0.00..10.27 rows=11 width=32) (actual time=0.003..0.009 rows=11 loops=42326)

  • Index Cond: (contract_id = as_start.contract_id)