explain.depesz.com

PostgreSQL's explain analyze made readable

Result: uDl6

Settings
# exclusive inclusive rows x rows loops node
1. 20.193 6,629.946 ↑ 1.0 19,871 1

Nested Loop (cost=19,889.69..299,070.24 rows=20,621 width=82) (actual time=965.395..6,629.946 rows=19,871 loops=1)

2. 951.515 1,913.809 ↑ 1.4 5,848 1

Bitmap Heap Scan on orders entity (cost=19,889.26..46,609.44 rows=8,313 width=16) (actual time=964.416..1,913.809 rows=5,848 loops=1)

  • Heap Blocks: exact=2253 lossy=11234
3. 10.893 962.294 ↓ 0.0 0 1

BitmapAnd (cost=19,889.26..19,889.26 rows=8,313 width=0) (actual time=962.294..962.294 rows=0 loops=1)

4. 916.205 916.205 ↓ 1.0 202,346 1

Bitmap Index Scan on idx_orders_tx_reference_time (cost=0..8,632.5 rows=195,607 width=0) (actual time=916.205..916.205 rows=202,346 loops=1)

  • Index Cond: ((reference_time >= '2020-02-20 08:00:00+00'::timestamp with time zone) AND (reference_time <= '2020-02-27 07:00:00+00'::timestamp with time zone))
5. 35.196 35.196 ↓ 1.1 154,914 1

Bitmap Index Scan on idx_orders_tx_org (cost=0..11,252.35 rows=146,106 width=0) (actual time=35.196..35.196 rows=154,914 loops=1)

  • Index Cond: (organization_id = 'e650cbea-3d63-4020-b8ae-73895a3d628d'::uuid)
6. 4,695.944 4,695.944 ↑ 2.7 3 5,848

Index Scan using idx_items_tx_order on order_items item (cost=0.43..30.29 rows=8 width=82) (actual time=0.793..0.803 rows=3 loops=5,848)

  • Index Cond: (order_id = entity.order_id)
Planning time : 0.422 ms
Execution time : 6,632.198 ms