explain.depesz.com

A tool for finding a real cause for slow queries.

Result: sNP

options
Did it help? Consider supporting us - Bitcoin address: 12v2hUztAk2LgzQ9H9LMwuU32urHMjZQnq
# exclusive inclusive rows x rows loops node
1. 754.430 28,283.969 ↑ 1.0 100,000 1

Limit (cost=85,847.22..92,513.15 rows=100,000 width=28) (actual time=24,972.514..28,283.969 rows=100,000 loops=1)

2. 1,080.676 27,529.539 ↑ 642.9 100,000 1

Hash Join (cost=85,847.22..4,371,045.75 rows=64,285,080 width=28) (actual time=24,972.505..27,529.539 rows=100,000 loops=1)

  • Hash Cond: (i.fk_weather_station_id = ws.id)
3. 858.036 26,440.213 ↑ 642.9 100,000 1

Hash Join (cost=85,811.37..2,683,526.55 rows=64,285,080 width=24) (actual time=24,963.820..26,440.213 rows=100,000 loops=1)

  • Hash Cond: (v.id = i.id)
4. 629.477 629.477 ↑ 642.9 100,000 1

Seq Scan on native_weather_data_value v (cost=0.00..1,312,013.58 rows=64,285,080 width=12) (actual time=10.493..629.477 rows=100,000 loops=1)

  • Filter: (((value)::text <> '-'::text) AND ((value)::text ~ '^[-0-9.]+$'::text))
5. 12,525.312 24,952.700 ↑ 1.0 2,972,372 1

Hash (cost=48,656.72..48,656.72 rows=2,972,372 width=16) (actual time=24,952.700..24,952.700 rows=2,972,372 loops=1)

  • Buckets: 524288 Batches: 1 Memory Usage: 139330kB
6. 12,427.388 12,427.388 ↑ 1.0 2,972,372 1

Seq Scan on native_weather_data_index i (cost=0.00..48,656.72 rows=2,972,372 width=16) (actual time=14.292..12,427.388 rows=2,972,372 loops=1)

7. 4.387 8.650 ↑ 1.0 1,149 1

Hash (cost=21.49..21.49 rows=1,149 width=4) (actual time=8.650..8.650 rows=1,149 loops=1)

  • Buckets: 1024 Batches: 1 Memory Usage: 41kB
8. 4.263 4.263 ↑ 1.0 1,149 1

Seq Scan on weather_station ws (cost=0.00..21.49 rows=1,149 width=4) (actual time=0.009..4.263 rows=1,149 loops=1)