explain.depesz.com

PostgreSQL's explain analyze made readable

Result: pme6

Settings

Optimization(s) for this plan:

# exclusive inclusive rows x rows loops node
1. 193.437 16,433.697 ↑ 172.5 600,000 1

Gather (cost=1,000.00..759,987,067.22 rows=103,526,491 width=36) (actual time=0.511..16,433.697 rows=600,000 loops=1)

  • Workers Planned: 4
  • Workers Launched: 4
2. 14,440.566 16,240.260 ↑ 215.7 120,000 5

Nested Loop (cost=0.00..749,633,418.12 rows=25,881,623 width=36) (actual time=0.284..16,240.260 rows=120,000 loops=5)

  • Join Filter: ((days.date)::timestamp with time zone <@ es.valid)
  • Rows Removed by Join Filter: 20880000
3. 1,799.693 1,799.693 ↓ 1.0 10,500,000 5

Parallel Seq Scan on event_series es (cost=0.00..966,880.00 rows=10,149,656 width=55) (actual time=0.022..1,799.693 rows=10,500,000 loops=5)

  • Filter: ((key = 'health'::text) OR (key = 'arr'::text))
4. 0.001 0.001 ↑ 1,275.0 2 52,500,000

Seq Scan on days (cost=0.00..35.50 rows=2,550 width=4) (actual time=0.001..0.001 rows=2 loops=52,500,000)

Planning time : 0.197 ms
Execution time : 16,453.155 ms