explain.depesz.com

PostgreSQL's explain analyze made readable

Result: f52k : 234

Settings
# exclusive inclusive rows x rows loops node
1. 0.021 1,175.689 ↓ 0.0 0 1

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

  • Sort Key: t2.tp_timestamp
  • Sort Method: quicksort Memory: 25kB
2. 10.466 1,175.668 ↓ 0.0 0 1

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

  • Filter: (t2.point_in_staion_before AND (NOT t2.point_in_staion_now))
  • Rows Removed by Filter: 82727
3. 22.167 1,165.202 ↓ 10,340.9 82,727 1

Result (cost=0.00..76.62 rows=8 width=26) (actual time=0.160..1,165.202 rows=82,727 loops=1)

4. 12.199 1,143.035 ↓ 10,340.9 82,727 1

Append (cost=0.00..76.54 rows=8 width=16) (actual time=0.159..1,143.035 rows=82,727 loops=1)

5. 0.006 0.006 ↓ 0.0 0 1

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

  • Filter: ((tp_timestamp >= '2019-01-01 00:00:00'::timestamp without time zone) AND (tp_timestamp < '2019-01-11 00:00:00'::timestamp without time zone) AND (tp_unit_id = 1182) AND (tp_status = 'A'::bpchar))
6. 1,130.830 1,130.830 ↓ 11,818.1 82,727 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.152..1,130.830 rows=82,727 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-11 00:00:00'::timestamp without time zone) AND (tp_status = 'A'::bpchar))