explain.depesz.com

A tool for finding a real cause for slow queries.

Result: mvG

options
Did it help? Consider supporting us - Bitcoin address: 12v2hUztAk2LgzQ9H9LMwuU32urHMjZQnq
# exclusive inclusive rows x rows loops node
1. 86.353 689.727 ↑ 1.0 69597 1

Hash Semi Join (cost=22895.12..31961.95 rows=69597 width=32) (actual time=405.078..689.727 rows=69597 loops=1)

  • Hash Cond: ((i.ticket_id)::integer = tickets.ticket_id)
2. 139.103 542.949 ↑ 1.0 69597 1

Hash Left Join (cost=19537.29..26777.20 rows=69597 width=36) (actual time=344.640..542.949 rows=69597 loops=1)

  • Hash Cond: ((r.issue_id)::integer = i.issue_id)
3. 60.167 60.167 ↑ 1.0 69597 1

Seq Scan on requests r (cost=0.00..3370.97 rows=69597 width=36) (actual time=0.004..60.167 rows=69597 loops=1)

4. 172.461 343.679 ↑ 1.0 372813 1

Hash (cost=13420.13..13420.13 rows=372813 width=8) (actual time=343.679..343.679 rows=372813 loops=1)

  • Buckets: 32768 Batches: 2 Memory Usage: 5116kB
5. 171.218 171.218 ↑ 1.0 372813 1

Seq Scan on issues i (cost=0.00..13420.13 rows=372813 width=8) (actual time=0.004..171.218 rows=372813 loops=1)

6. 29.530 60.425 ↑ 1.0 70570 1

Hash (cost=2475.70..2475.70 rows=70570 width=4) (actual time=60.425..60.425 rows=70570 loops=1)

  • Buckets: 8192 Batches: 1 Memory Usage: 1654kB
7. 30.895 30.895 ↑ 1.0 70570 1

Seq Scan on tickets (cost=0.00..2475.70 rows=70570 width=4) (actual time=0.005..30.895 rows=70570 loops=1)