explain.depesz.com

PostgreSQL's explain analyze made readable

Result: y3hg : routing_esme_interval

Settings
# exclusive inclusive rows x rows loops node
1. 0.394 17.512 ↑ 1.0 1,000 1

Limit (cost=0.01..167.81 rows=1,000 width=268) (actual time=0.095..17.512 rows=1,000 loops=1)

  • Buffers: shared hit=143
2. 10.788 17.118 ↑ 876,820.0 1,000 1

Nested Loop (cost=0.01..147,133,669.21 rows=876,820,000 width=268) (actual time=0.093..17.118 rows=1,000 loops=1)

  • Buffers: shared hit=143
3. 0.885 4.724 ↑ 10,919.3 803 1

Nested Loop (cost=0.01..266,319.20 rows=8,768,200 width=104) (actual time=0.055..4.724 rows=803 loops=1)

  • Buffers: shared hit=143
4. 0.195 0.889 ↑ 148.6 590 1

Append (cost=0.00..90,955.20 rows=87,682 width=72) (actual time=0.042..0.889 rows=590 loops=1)

  • Buffers: shared hit=143
5. 0.023 0.023 ↓ 0.0 0 1

Seq Scan on routing r (cost=0.00..0.00 rows=1 width=72) (actual time=0.023..0.023 rows=0 loops=1)

  • Filter: ((endtime >= 1549178971) AND (endtime <= 1549265371))
6. 0.671 0.671 ↑ 83.9 590 1

Index Scan using route_routing_1549144800_endtime_idx on routing_1549144800 r_1 (cost=0.43..51,120.00 rows=49,518 width=72) (actual time=0.018..0.671 rows=590 loops=1)

  • Index Cond: ((endtime >= 1549178971) AND (endtime <= 1549265371))
  • Buffers: shared hit=143
7. 0.000 0.000 ↓ 0.0 0

Index Scan using route_routing_1549231200_endtime_idx on routing_1549231200 r_2 (cost=0.43..39,396.79 rows=38,163 width=72) (never executed)

  • Index Cond: ((endtime >= 1549178971) AND (endtime <= 1549265371))
8. 2.950 2.950 ↑ 100.0 1 590

Function Scan on jsonb_each esme (cost=0.01..1.00 rows=100 width=64) (actual time=0.005..0.005 rows=1 loops=590)

9. 1.606 1.606 ↑ 100.0 1 803

Function Scan on jsonb_each pricing (cost=0.01..1.00 rows=100 width=64) (actual time=0.002..0.002 rows=1 loops=803)