explain.depesz.com

A tool for finding a real cause for slow queries.

Result: hQDB

options
Did it help? Consider supporting us - Bitcoin address: 12v2hUztAk2LgzQ9H9LMwuU32urHMjZQnq
# exclusive inclusive rows x rows loops node
1. 432.621 5,813.166 ↓ 2.6 265,494 1

Hash Join (cost=11,251.650..222,009.130 rows=101,599 width=4) (actual time=116.086..5,813.166 rows=265,494 loops=1)

  • Hash Cond: (seven.four = papa.quebec)
2. 5,098.237 5,264.819 ↓ 2.9 297,500 1

Nested Loop Semi Join (cost=0.000..208,598.510 rows=101,599 width=4) (actual time=0.159..5,264.819 rows=297,500 loops=1)

  • -> Index Scan using tracking_history_vid_index on tracking_history (cost=0.00..1.81 rows=11 width=4) (actual time=0.004..0.004 rows=0 loops=105
3. 166.582 166.582 ↑ 1.0 1,050,000 1

Seq Scan on bravo seven (cost=0.000..20,314.230 rows=1,050,023 width=8) (actual time=0.008..166.582 rows=1,050,000 loops=1)

  • Index Cond: (golf.echo = seven.echo)
  • Filter: ((golf.alpha >= 'foxtrot'::timestamp with time zone) AND (golf.lima >= 500))
4. 58.868 115.726 ↑ 1.0 218,251 1

Hash (cost=8,523.510..8,523.510 rows=218,251 width=4) (actual time=115.726..115.726 rows=218,251 loops=1)

5. 56.858 56.858 ↑ 1.0 218,251 1

Seq Scan on romeo papa (cost=0.000..8,523.510 rows=218,251 width=4) (actual time=0.005..56.858 rows=218,251 loops=1)