explain.depesz.com

PostgreSQL's explain analyze made readable

Result: fDuk : 123

Settings
# exclusive inclusive rows x rows loops node
1. 0.007 190.655 ↓ 0.0 0 1

Sort (cost=76.71..76.71 rows=2 width=16) (actual time=190.655..190.655 rows=0 loops=1)

  • Sort Key: t2.tp_timestamp
  • Sort Method: quicksort Memory: 25kB
2. 5.554 190.648 ↓ 0.0 0 1

Subquery Scan on t2 (cost=0.00..76.70 rows=2 width=16) (actual time=190.648..190.648 rows=0 loops=1)

  • Filter: (t2.point_in_staion_before AND (NOT t2.point_in_staion_now))
  • Rows Removed by Filter: 82732
3. 12.837 185.094 ↓ 10,341.5 82,732 1

Result (cost=0.00..76.62 rows=8 width=26) (actual time=0.045..185.094 rows=82,732 loops=1)

4. 6.699 172.257 ↓ 10,341.5 82,732 1

Append (cost=0.00..76.54 rows=8 width=16) (actual time=0.044..172.257 rows=82,732 loops=1)

5. 0.004 0.004 ↓ 0.0 0 1

Seq Scan on uzgps_track_point tp (cost=0.00..0.00 rows=1 width=16) (actual time=0.004..0.004 rows=0 loops=1)

  • Filter: ((tp_timestamp >= '2019-01-01 00:00:00'::timestamp without time zone) AND (tp_timestamp < '2019-01-22 00:00:00'::timestamp without time zone) AND (tp_unit_id = 1182) AND (tp_status = 'A'::bpchar))
6. 165.554 165.554 ↓ 11,818.9 82,732 1

Index Scan using uzgps_track_point_2019m01_tp_unit_id_tp_timestamp_tp_status_idx on uzgps_track_point_2019m01 tp_1 (cost=0.56..76.54 rows=7 width=16) (actual time=0.040..165.554 rows=82,732 loops=1)

  • Index Cond: ((tp_unit_id = 1182) AND (tp_timestamp >= '2019-01-01 00:00:00'::timestamp without time zone) AND (tp_timestamp < '2019-01-22 00:00:00'::timestamp without time zone) AND (tp_status = 'A'::bpchar))