explain.depesz.com

PostgreSQL's explain analyze made readable

Result: asr3

Settings
# exclusive inclusive rows x rows loops node
1. 0.048 129.523 ↑ 1.0 1 1
→

Aggregate (cost=34,728.84..34,728.85 rows=1 width=152) (actual time=129.523..129.523 rows=1 loops=1)

2. 1.493 129.475 ↓ 2.4 12 1
→

Hash Join (cost=121.95..34,728.67 rows=5 width=81) (actual time=23.795..129.475 rows=12 loops=1)

  • Hash Cond: ((i.incident_id)::text = (ir.incident_id)::text)
3. 127.791 127.791 ↓ 1.2 8,294 1
→

Seq Scan on incident i (cost=0.00..34,581.22 rows=6,787 width=53) (actual time=0.070..127.791 rows=8,294 loops=1)

  • Filter: (((status)::text = 'COMPLETED'::text) AND ((type)::text = 'RR_TEST_AUTOMATION.HTTP_RRTESTAUTOMATION_RRHTTPFieldNameWithSpecialChar1'::text))
  • Rows Removed by Filter: 202454
4. 0.049 0.191 ↓ 1.3 204 1
→

Hash (cost=119.97..119.97 rows=158 width=102) (actual time=0.191..0.191 rows=204 loops=1)

  • Buckets: 1024 Batches: 1 Memory Usage: 36kB
5. 0.142 0.142 ↓ 1.3 204 1
→

Index Scan using time_started_idx on incident_resolution ir (cost=0.42..119.97 rows=158 width=102) (actual time=0.019..0.142 rows=204 loops=1)

  • Index Cond: ((time_started > '1565589600000'::bigint) AND (time_started < '1565596800000'::bigint))
  • Filter: ((time_completed < '1565596800000'::bigint) AND (time_completed <> 0))
Planning time : 0.413 ms