explain.depesz.com

A tool for finding a real cause for slow queries.

Result: Zpi

options
Did it help? Consider supporting us - Bitcoin address: 12v2hUztAk2LgzQ9H9LMwuU32urHMjZQnq
# exclusive inclusive rows x rows loops node
1. 0.000 0.000 ↓ 0.0

Hash Join (cost=20,760,528.71..83,760,632.51 rows=123,375,160 width=89) (actual time=.. rows= loops=)

  • Hash Cond: (usnob1.usno_id = usno_blend.usno_id)
2. 0.000 0.000 ↓ 0.0

Seq Scan on usnob1 (cost=0.00..7,356,319.20 rows=246,750,320 width=79) (actual time=.. rows= loops=)

3. 0.000 0.000 ↓ 0.0

Hash (cost=17,031,035.51..17,031,035.51 rows=148,023,296 width=75) (actual time=.. rows= loops=)

4. 0.000 0.000 ↓ 0.0

Hash Join (cost=3,944,783.35..17,031,035.51 rows=148,023,296 width=75) (actual time=.. rows= loops=)

  • Hash Cond: (usno_blend.usno_id = xmatch_final.usno_id)
5. 0.000 0.000 ↓ 0.0

Seq Scan on usno_blend (cost=0.00..6,202,149.92 rows=296,046,592 width=23) (actual time=.. rows= loops=)

6. 0.000 0.000 ↓ 0.0

Hash (cost=3,016,113.15..3,016,113.15 rows=41,708,656 width=52) (actual time=.. rows= loops=)

7. 0.000 0.000 ↓ 0.0

Group (cost=0.00..2,599,026.59 rows=41,708,656 width=13) (actual time=.. rows= loops=)

8. 0.000 0.000 ↓ 0.0

Index Scan using xmatch_final_usnoid_idx on xmatch_final (cost=0.00..2,494,754.95 rows=41,708,656 width=13) (actual time=.. rows= loops=)