explain.depesz.com

PostgreSQL's explain analyze made readable

Result: JDSb : Optimization for: plan #qDOD

Settings

Optimization path:

# exclusive inclusive rows x rows loops node
1. 0.613 0.834 ↓ 2.0 2 1

Update (cost=0.00..6.89 rows=1 width=1) (actual time=0.237..0.834 rows=2 loops=1)

  • (slice0) Executor memory: 313K bytes avg x 2 workers, 313K bytes max (seg0).Memory used: 128000kBOptimizer: Pivotal Optimizer (GPORCA) version 3.80.0
2. 0.003 0.221 ↓ 2.0 2 1

Result (cost=0.00..6.00 rows=1 width=228) (actual time=0.207..0.221 rows=2 loops=1)

3. 0.004 0.218 ↓ 2.0 2 1

Split (cost=0.00..6.00 rows=1 width=224) (actual time=0.205..0.218 rows=2 loops=1)

4. 0.004 0.214 ↑ 1.0 1 1

Result (cost=0.00..6.00 rows=1 width=260) (actual time=0.203..0.214 rows=1 loops=1)

5. 0.210 0.210 ↑ 1.0 1 1

Index Scan using salert_posts_pkey on salert_posts (cost=0.00..6.00 rows=1 width=494) (actual time=0.199..0.210 rows=1 loops=1)

  • Index Cond: ((id)::text = '1219966077318418432'::text)
Planning time : 11.543 ms
Execution time : 24.297 ms