explain.depesz.com

PostgreSQL's explain analyze made readable

Result: vkzm : OSM Performance - Waterways near Roads Original

Settings
# exclusive inclusive rows x rows loops node
1. 8,399.636 639,758.640 ↑ 3,020.0 788,668 1

Gather (cost=1,000.66..9,365,923,194.93 rows=2,381,748,434 width=408) (actual time=1.861..639,758.640 rows=788,668 loops=1)

  • Workers Planned: 3
  • Workers Launched: 3
  • Buffers: shared hit=39705733
2. 4,238.203 631,359.004 ↑ 3,896.7 197,167 4 / 4

Nested Loop (cost=0.66..9,127,747,351.53 rows=768,305,946 width=408) (actual time=3.989..631,359.004 rows=197,167 loops=4)

  • Buffers: shared hit=39705733
3. 871.379 871.379 ↑ 1.3 1,605,768 4 / 4

Parallel Seq Scan on road_line r (cost=0.00..268,350.20 rows=2,071,820 width=233) (actual time=0.018..871.379 rows=1,605,768 loops=4)

  • Buffers: shared hit=247632
4. 626,249.422 626,249.422 ↓ 0.0 0 6,423,071 / 4

Index Scan using gix_osm_waterway_line on waterway_line wl (cost=0.66..4,403.78 rows=176 width=408) (actual time=0.264..0.390 rows=0 loops=6,423,071)

  • Index Cond: (way && st_expand(r.way, '15'::double precision))
  • Filter: st_dwithin(r.way, way, '15'::double precision)
  • Rows Removed by Filter: 1
  • Buffers: shared hit=39436339
Planning time : 1.761 ms
Execution time : 639,967.189 ms