explain.depesz.com

PostgreSQL's explain analyze made readable

Result: pn6i : get osm_id per point

Settings

Optimization path:

Optimization(s) for this plan:

# exclusive inclusive rows x rows loops node
1. 86.849 599.640 ↑ 1.0 237,454 1

Gather (cost=38,397.33..79,659.14 rows=237,454 width=45) (actual time=393.714..599.640 rows=237,454 loops=1)

  • Workers Planned: 2
  • Workers Launched: 2
2. 179.024 512.791 ↑ 1.3 79,151 3 / 3

Parallel Hash Left Join (cost=37,397.33..54,913.74 rows=98,939 width=45) (actual time=394.116..512.791 rows=79,151 loops=3)

  • Hash Cond: (points.segment_id = planet.id)
3. 48.438 48.438 ↑ 1.3 79,151 3 / 3

Parallel Seq Scan on points (cost=0.00..12,803.39 rows=98,939 width=45) (actual time=0.016..48.438 rows=79,151 loops=3)

4. 146.346 285.329 ↑ 1.3 358,767 3 / 3

Parallel Hash (cost=29,601.59..29,601.59 rows=448,459 width=16) (actual time=285.329..285.329 rows=358,767 loops=3)

  • Buckets: 131072 Batches: 32 Memory Usage: 2688kB
5. 138.983 138.983 ↑ 1.3 358,767 3 / 3

Parallel Seq Scan on planet_osm_line_segments planet (cost=0.00..29,601.59 rows=448,459 width=16) (actual time=0.244..138.983 rows=358,767 loops=3)

Planning time : 0.148 ms
Execution time : 614.743 ms