explain.depesz.com

A tool for finding a real cause for slow queries.

Result: rDT

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=4,151.30..12,644.94 rows=82,834 width=45) (actual time=.. rows= loops=)

  • Output: o.id, s.status
  • Hash Cond: ((o.lastoperationstatus_id)::text = (s.id)::text)
2. 0.000 0.000 ↓ 0.0

Seq Scan on public.xselloperation o (cost=0.00..3,901.69 rows=88,869 width=74) (actual time=.. rows= loops=)

  • Output: o.id, o.lastoperationstatus_id
3. 0.000 0.000 ↓ 0.0

Hash (cost=2,388.69..2,388.69 rows=82,769 width=45) (actual time=.. rows= loops=)

  • Output: s.status, s.id
4. 0.000 0.000 ↓ 0.0

Seq Scan on public.xselloperationstatus s (cost=0.00..2,388.69 rows=82,769 width=45) (actual time=.. rows= loops=)

  • Output: s.status, s.id