explain.depesz.com

A tool for finding a real cause for slow queries.

Result: 4Eo : 2idx

options
Did it help? Consider supporting us - Bitcoin address: 12v2hUztAk2LgzQ9H9LMwuU32urHMjZQnq
# exclusive inclusive rows x rows loops node
1. 5,816.185 86,452.995 ↓ 752,314.0 752,314 1

HashAggregate (cost=619,813.12..619,813.13 rows=1 width=104) (actual time=85,888.788..86,452.995 rows=752,314 loops=1)

  • Buffers: shared hit=10547158 read=40977
2. 3,358.728 80,636.810 ↓ 2,178,784.0 2,178,784 1

Nested Loop (cost=0.00..619,813.09 rows=1 width=104) (actual time=438.354..80,636.810 rows=2,178,784 loops=1)

  • Join Filter: ((i1.id_portion)::text = t1.id_portion)
  • Buffers: shared hit=10547158 read=40977
3. 2,826.938 24,517.205 ↓ 917.8 1,352,843 1

Subquery Scan on t1 (cost=0.00..612,349.42 rows=1,474 width=68) (actual time=438.294..24,517.205 rows=1,352,843 loops=1)

  • Filter: ((t1.nd)::text ~~ '%/__0612/%'::text)
  • Buffers: shared hit=2154020 read=40612
4. 10,791.429 21,690.267 ↑ 1.0 5,685,117 1

WindowAgg (cost=0.00..535,600.34 rows=5,685,117 width=43) (actual time=399.633..21,690.267 rows=5,685,117 loops=1)

  • Buffers: shared hit=2154020 read=40612
5. 10,898.838 10,898.838 ↑ 1.0 5,685,117 1

Index Scan using dclcont_idx2 on dclcont (cost=0.00..416,212.88 rows=5,685,117 width=43) (actual time=399.597..10,898.838 rows=5,685,117 loops=1)

  • Buffers: shared hit=2154020 read=40612
6. 52,760.877 52,760.877 ↓ 2.0 2 1,352,843

Index Scan using dclcont_idx2 on dclcont i1 (cost=0.00..5.04 rows=1 width=111) (actual time=0.037..0.039 rows=2 loops=1,352,843)

  • Index Cond: (((nd)::text = (t1.nd)::text) AND (g32 = t1.g32) AND (nzp = t1.nzp))
  • Buffers: shared hit=8393138 read=365