explain.depesz.com

A tool for finding a real cause for slow queries.

Result: rBy

options
Did it help? Consider supporting us - Bitcoin address: 12v2hUztAk2LgzQ9H9LMwuU32urHMjZQnq
# exclusive inclusive rows x rows loops node
1. 0.552 1,954.266 ↓ 424.0 424 1

Nested Loop (cost=24.62..47.18 rows=1 width=145) (actual time=1,893.867..1,954.266 rows=424 loops=1)

2. 0.097 1,907.074 ↓ 424.0 424 1

Nested Loop (cost=24.62..45.28 rows=1 width=69) (actual time=1,893.813..1,907.074 rows=424 loops=1)

3. 0.337 1,895.529 ↓ 424.0 424 1

Nested Loop (cost=24.62..41.87 rows=1 width=41) (actual time=1,893.790..1,895.529 rows=424 loops=1)

  • Join Filter: (x.r = (min(x.r)))
4. 2.016 1,893.920 ↓ 84.8 424 1

HashAggregate (cost=24.62..24.69 rows=5 width=12) (actual time=1,893.766..1,893.920 rows=424 loops=1)

5. 1.465 1,891.904 ↓ 85.2 426 1

Nested Loop (cost=0.00..24.58 rows=5 width=12) (actual time=0.051..1,891.904 rows=426 loops=1)

6. 0.671 0.671 ↓ 84.8 424 1

Index Scan using dr8_runfieldcamcol_idx on dr8 (cost=0.00..7.46 rows=5 width=8) (actual time=0.038..0.671 rows=424 loops=1)

  • Index Cond: ((run = 211) AND (field = 356) AND (camcol = 4))
7. 1,889.768 1,889.768 ↑ 1.0 1 424

Index Scan using xmatch_final_objid_idx on xmatch_final x (cost=0.00..3.41 rows=1 width=12) (actual time=4.446..4.457 rows=1 loops=424)

  • Index Cond: (x.objid = public.dr8.objid)
8. 1.272 1.272 ↑ 1.0 1 424

Index Scan using xmatch_final_objid_idx on xmatch_final x (cost=0.00..3.41 rows=1 width=25) (actual time=0.003..0.003 rows=1 loops=424)

  • Index Cond: (x.objid = x.objid)
9. 11.448 11.448 ↑ 1.0 1 424

Index Scan using dr8_pkey on dr8 (cost=0.00..3.39 rows=1 width=44) (actual time=0.026..0.027 rows=1 loops=424)

  • Index Cond: (public.dr8.objid = x.objid)
10. 46.640 46.640 ↑ 1.0 1 424

Index Scan using usno_merged_id_idx on usno_merged (cost=0.00..1.89 rows=1 width=89) (actual time=0.109..0.110 rows=1 loops=424)

  • Index Cond: (usno_merged.usno_id = x.usno_id)