explain.depesz.com

A tool for finding a real cause for slow queries.

Result: ORK

options
Did it help? Consider supporting us - Bitcoin address: 12v2hUztAk2LgzQ9H9LMwuU32urHMjZQnq
# exclusive inclusive rows x rows loops node
1. 0.062 113,381.486 ↑ 1.0 50 1

Limit (cost=12,404.28..12,404.78 rows=50 width=125) (actual time=113,381.359..113,381.486 rows=50 loops=1)

2. 106.383 113,381.424 ↑ 261.9 50 1

HashAggregate (cost=12,404.28..12,535.25 rows=13,097 width=125) (actual time=113,381.356..113,381.424 rows=50 loops=1)

3. 78,260.484 113,275.041 ↓ 3.5 45,209 1

Nested Loop (cost=3,589.12..12,306.06 rows=13,097 width=125) (actual time=0.798..113,275.041 rows=45,209 loops=1)

  • Join Filter: (cdm.hier_orig_node_num ~~* ANY (hdm.original_node_num))
4. 3.622 3.732 ↓ 197.5 1,185 1

Bitmap Heap Scan on hdm_05_tdct_csr hdm (cost=4.30..15.07 rows=6 width=32) (actual time=0.121..3.732 rows=1,185 loops=1)

  • Recheck Cond: (level1 = 1)
5. 0.110 0.110 ↓ 197.5 1,185 1

Bitmap Index Scan on hdm_05_tdct_csr_level1_index (cost=0.00..4.30 rows=6 width=0) (actual time=0.110..0.110 rows=1,185 loops=1)

  • Index Cond: (level1 = 1)
6. 34,951.377 35,010.825 ↓ 1.0 45,209 1,185

Materialize (cost=3,584.82..4,031.29 rows=44,647 width=129) (actual time=0.001..29.545 rows=45,209 loops=1,185)

7. 59.448 59.448 ↓ 1.0 45,209 1

Seq Scan on rdm_05_test2_rdm cdm (cost=0.00..3,540.18 rows=44,647 width=129) (actual time=0.008..59.448 rows=45,209 loops=1)

  • Filter: ((case_date >= 20111101) AND (case_date <= 20120131))