explain.depesz.com

A tool for finding a real cause for slow queries.

Result: KXd

options
Did it help? Consider supporting us - Bitcoin address: 12v2hUztAk2LgzQ9H9LMwuU32urHMjZQnq
# exclusive inclusive rows x rows loops node
1. 0.105 50,440.891 ↑ 3.9 15 1

Sort (cost=28,354.02..28,354.16 rows=58 width=42) (actual time=50,440.882..50,440.891 rows=15 loops=1)

  • Sort Key: d.det_indexvalue
2. 17.318 50,440.786 ↑ 3.9 15 1

Nested Loop (cost=30.78..28,352.32 rows=58 width=42) (actual time=878.610..50,440.786 rows=15 loops=1)

3. 66.146 4,899.836 ↓ 49.8 4,578 1

Nested Loop (cost=30.78..25,581.00 rows=92 width=32) (actual time=782.595..4,899.836 rows=4,578 loops=1)

4. 79.620 88.206 ↓ 9.4 24,588 1

Bitmap Heap Scan on img_pageindex b (cost=30.78..9,705.91 rows=2,629 width=12) (actual time=10.503..88.206 rows=24,588 loops=1)

  • Recheck Cond: (((ref_indexcode)::text = 'BTO'::text) AND ((det_indexvalue)::text = 'MACS'::text))
5. 8.586 8.586 ↓ 9.4 24,588 1

Bitmap Index Scan on x_img_pageindex_code_value (cost=0.00..30.78 rows=2,629 width=0) (actual time=8.586..8.586 rows=24,588 loops=1)

  • Index Cond: (((ref_indexcode)::text = 'BTO'::text) AND ((det_indexvalue)::text = 'MACS'::text))
6. 4,745.484 4,745.484 ↓ 0.0 0 24,588

Index Scan using x_img_pageevent_hdr_intdocid_pev_date on img_pageevent e (cost=0.00..6.03 rows=1 width=20) (actual time=0.081..0.193 rows=0 loops=24,588)

  • Index Cond: ((("outer".hdr_intdocid)::text = (e.hdr_intdocid)::text) AND (e.pev_date >= '2012-04-10 00:00:00'::timestamp without time zone) AND (e.pev_date <= '2012-04-22 23:59:59.9999'::timestamp without time zone))
  • Filter: ((ety_code)::text = 'STORE'::text)
7. 45,523.632 45,523.632 ↓ 0.0 0 4,578

Index Scan using img_pageindex_pkey on img_pageindex d (cost=0.00..30.11 rows=1 width=34) (actual time=9.944..9.944 rows=0 loops=4,578)

  • Index Cond: (((d.hdr_intdocid)::text = ("outer".hdr_intdocid)::text) AND (d.det_sequence = 0))
  • Filter: ((ref_indexcode)::text = 'MBL'::text)