explain.depesz.com

A tool for finding a real cause for slow queries.

Result: 9Tk

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

Subquery Scan on seatlist (cost=121,287.87..121,298.13 rows=342 width=40) (actual time=1,437.590..1,437.590 rows=0 loops=1)

2. 1.469 1,437.589 ↓ 0.0 0 1

HashAggregate (cost=121,287.87..121,294.71 rows=342 width=20) (actual time=1,437.589..1,437.589 rows=0 loops=1)

  • Filter: (array_length(array_agg(foo.seat_location), 1) < 4)
3. 108.946 1,436.120 ↑ 1.9 1,833 1

Subquery Scan on foo (cost=0.00..121,245.18 rows=3,415 width=20) (actual time=50.987..1,436.120 rows=1,833 loops=1)

  • Filter: (foo.section_id = 115176)
4. 704.634 1,327.174 ↑ 1.0 682,969 1

WindowAgg (cost=0.00..112,708.07 rows=682,969 width=12) (actual time=0.032..1,327.174 rows=682,969 loops=1)

5. 622.540 622.540 ↑ 1.0 682,969 1

Index Scan using seating_seats_search on seating_seats (cost=0.00..93,926.42 rows=682,969 width=12) (actual time=0.019..622.540 rows=682,969 loops=1)