explain.depesz.com

A tool for finding a real cause for slow queries.

Result: DN

options
Did it help? Consider supporting us - Bitcoin address: 12v2hUztAk2LgzQ9H9LMwuU32urHMjZQnq
# exclusive inclusive rows x rows loops node
1. 50.105 841.478 ↓ 0.0 0 1

Merge Join (cost=125,379.14..125,775.12 rows=3,311 width=29) (actual time=841.478..841.478 rows=0 loops=1)

  • Merge Cond: (a.orderid = b.orderid)
  • Total runtime: 842.134 ms
2. 161.744 774.475 ↑ 3.4 16,815 1

Sort (cost=109,737.32..109,881.89 rows=57,828 width=23) (actual time=736.163..774.475 rows=16,815 loops=1)

  • Sort Key: a.orderid
  • Sort Method: quicksort Memory: 1695kB
3. 587.698 612.731 ↑ 3.4 16,815 1

Bitmap Heap Scan on orderitemattribute a (cost=1,286.88..105,163.27 rows=57,828 width=23) (actual time=41.536..612.731 rows=16,815 loops=1)

  • Recheck Cond: ((attributeid)::text = 'display-album'::text)
4. 25.033 25.033 ↑ 3.4 16,815 1

Bitmap Index Scan on (cost=0.00..1,272.43 rows=57,828 width=0) (actual time=25.033..25.033 rows=16,815 loops=1)

  • Index Cond: ((attributeid)::text = 'display-album'::text)
5. 8.418 16.898 ↑ 13.3 1,109 1

Sort (cost=15,641.81..15,678.73 rows=14,769 width=14) (actual time=14.471..16.898 rows=1,109 loops=1)

  • Sort Key: b.orderid
  • Sort Method: quicksort Memory: 76kB
6. 7.049 8.480 ↑ 13.3 1,114 1

Bitmap Heap Scan on orderitem b (cost=310.96..14,619.03 rows=14,769 width=14) (actual time=1.865..8.480 rows=1,114 loops=1)

  • Recheck Cond: ((productid)::text = 'ModernBook'::text)
7. 1.431 1.431 ↑ 13.3 1,114 1

Bitmap Index Scan on id_orderitem_productid (cost=0.00..307.27 rows=14,769 width=0) (actual time=1.431..1.431 rows=1,114 loops=1)

  • Index Cond: ((productid)::text = 'ModernBook'::text)