explain.depesz.com

PostgreSQL's explain analyze made readable

Result: 3Q3u

Settings
# exclusive inclusive rows x rows loops node
1. 0.450 57.837 ↑ 1.0 1 1

Aggregate (cost=34,771.48..34,771.49 rows=1 width=8) (actual time=57.837..57.837 rows=1 loops=1)

2. 2.757 57.387 ↓ 3.0 4,989 1

Nested Loop (cost=509.98..34,767.38 rows=1,640 width=0) (actual time=3.899..57.387 rows=4,989 loops=1)

3. 34.586 34.586 ↓ 1.3 5,011 1

Bitmap Heap Scan on tour_schedules (cost=509.55..2,698.44 rows=3,916 width=4) (actual time=3.855..34.586 rows=5,011 loops=1)

  • Recheck Cond: ((tour_date < '2019-08-12'::date) AND (tour_shipments_counter_cache > 0))
  • Filter: ((name)::text ~~* '%berlin%'::text)
  • Rows Removed by Filter: 16669
  • Heap Blocks: exact=1777
  • -> Bitmap Index Scan on index_tour_schedules_on_tour_date_and_pick_up_address_id_and_id (cost=0.00..508.57 rows=21937 width=0) (actual time=3.321..3.321 rows=21763 loop
  • Index Cond: (tour_date < '2019-08-12'::date)
4. 20.044 20.044 ↑ 1.0 1 5,011

Index Scan using addresses_pkey on addresses (cost=0.43..8.18 rows=1 width=4) (actual time=0.004..0.004 rows=1 loops=5,011)

  • Index Cond: (id = tour_schedules.pick_up_address_id)
  • Filter: ((city)::text ~~* '%berlin%'::text)
  • Rows Removed by Filter: 0
Planning time : 2.448 ms
Execution time : 57.988 ms