explain.depesz.com

A tool for finding a real cause for slow queries.

Result: b3q

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

Nested Loop Left Join (cost=0.00..22.60 rows=1 width=2343) (actual time=.. rows= loops=)

2. 0.000 0.000 ↓ 0.0

Nested Loop (cost=0.00..13.82 rows=1 width=2290) (actual time=.. rows= loops=)

  • Join Filter: ((poi.geometry && alsession.geometry) AND _st_intersects(poi.geometry, alsession.geometry))
3. 0.000 0.000 ↓ 0.0

Seq Scan on poi (cost=0.00..3.99 rows=1 width=677) (actual time=.. rows= loops=)

  • Filter: (featid = 89)
4. 0.000 0.000 ↓ 0.0

Index Scan using alsession_pkey on alsession (cost=0.00..9.57 rows=1 width=1613) (actual time=.. rows= loops=)

  • Index Cond: (((sessionid)::text >= '20120601000000'::text) AND ((sessionid)::text <= '20120601235959'::text))
  • Filter: ((NOT pending) AND (vehicleid = ANY ('{376,1465,7,1665,593,1669,103,3,67,1205,1277,1479,8,1275,526,184}'::integer[])))
5. 0.000 0.000 ↓ 0.0

Index Scan using "PK_Vehicle" on alvehicle (cost=0.00..8.27 rows=1 width=57) (actual time=.. rows= loops=)

  • Index Cond: (vehicleid = alsession.vehicleid)