explain.depesz.com

PostgreSQL's explain analyze made readable

Result: GoKd

Settings
# exclusive inclusive rows x rows loops node
1. 0.052 125.743 ↑ 1.0 1 1

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

2. 1.290 125.691 ↓ 2.4 12 1

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

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

Seq Scan on incident i (cost=0.00..34,581.22 rows=6,787 width=53) (actual time=0.077..124.216 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.046 0.185 ↓ 1.3 204 1

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

  • Buckets: 1024 Batches: 1 Memory Usage: 36kB
5. 0.139 0.139 ↓ 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.013..0.139 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.299 ms