explain.depesz.com

PostgreSQL's explain analyze made readable

Result: Imd9i

Settings
# exclusive inclusive rows x rows loops node
1. 2.887 103.882 ↓ 1.5 749 1

Sort (cost=5,946.94..5,948.21 rows=509 width=1,970) (actual time=103.799..103.882 rows=749 loops=1)

  • Sort Key: ((e.json ->> 'serverVersion'::text))
  • Sort Method: quicksort Memory: 1398kB
2. 5.061 100.995 ↓ 1.5 749 1

Nested Loop (cost=42.19..5,924.06 rows=509 width=1,970) (actual time=29.809..100.995 rows=749 loops=1)

3. 0.290 30.022 ↓ 1.5 749 1

Bitmap Heap Scan on event_metadata em (cost=41.77..1,865.55 rows=509 width=8) (actual time=29.768..30.022 rows=749 loops=1)

  • Recheck Cond: (((provider_id)::text = 'testsk'::text) AND (server_version >= 0))
  • Heap Blocks: exact=70
4. 29.732 29.732 ↓ 1.6 813 1

Bitmap Index Scan on event_metadata_sync_index (cost=0.00..41.64 rows=509 width=0) (actual time=29.732..29.732 rows=813 loops=1)

  • Index Cond: (((provider_id)::text = 'testsk'::text) AND (server_version >= 0))
5. 65.912 65.912 ↑ 1.0 1 749

Index Scan using event_pkey on event e (cost=0.42..7.97 rows=1 width=1,938) (actual time=0.088..0.088 rows=1 loops=749)

  • Index Cond: (id = em.event_id)
Planning time : 18.541 ms
Execution time : 104.039 ms