explain.depesz.com

PostgreSQL's explain analyze made readable

Result: kQr2

Settings

Optimization(s) for this plan:

# exclusive inclusive rows x rows loops node
1. 0.001 0.083 ↑ 2.0 1 1

Unique (cost=16.62..16.68 rows=2 width=205) (actual time=0.082..0.083 rows=1 loops=1)

2. 0.049 0.082 ↑ 2.0 1 1

Sort (cost=16.62..16.62 rows=2 width=205) (actual time=0.081..0.082 rows=1 loops=1)

  • Sort Key: s0.id, s0.identifier, s0.name, s0.description, s0.uuidv2, s0.alias, s0.status, s0.allow_frontend, s0.id, s0.organization_id, s0.created_at, s0.updated_at
  • Sort Method: quicksort Memory: 25kB
3. 0.001 0.033 ↑ 2.0 1 1

Append (cost=0.28..16.61 rows=2 width=205) (actual time=0.024..0.033 rows=1 loops=1)

4. 0.024 0.024 ↑ 1.0 1 1

Index Scan using index_scenarios_on_organization_id_and_alias on scenarios s0 (cost=0.28..8.29 rows=1 width=128) (actual time=0.023..0.024 rows=1 loops=1)

  • Index Cond: ((organization_id = 44) AND ((alias)::text = 'github_6'::text))
5. 0.008 0.008 ↓ 0.0 0 1

Index Scan using index_scenarios_on_uuidv2 on scenarios s0_1 (cost=0.28..8.29 rows=1 width=128) (actual time=0.008..0.008 rows=0 loops=1)

  • Index Cond: ((uuidv2)::text = 'github_6'::text)
  • Filter: (organization_id = 44)