explain.depesz.com

PostgreSQL's explain analyze made readable

Result: h6Ru

Settings
# exclusive inclusive rows x rows loops node
1. 0.000 0.000 ↓ 0.0

Limit (cost=1.43..5,627.72 rows=20 width=71) (actual rows= loops=)

2. 0.000 0.000 ↓ 0.0

Nested Loop (cost=1.43..24,194.50 rows=86 width=71) (actual rows= loops=)

  • Join Filter: (merge_requests.created_at >= issue_metrics.first_mentioned_in_commit_at)
3. 0.000 0.000 ↓ 0.0

Nested Loop (cost=0.99..24,008.50 rows=258 width=67) (actual rows= loops=)

4. 0.000 0.000 ↓ 0.0

Index Scan Backward using merge_requests_target_project_id_created_at_idx on merge_requests (cost=0.56..7,369.36 rows=4,508 width=63) (actual rows= loops=)

  • Index Cond: ((target_project_id = 13083) AND (created_at >= '2019-06-21 10:43:57.676885+00'::timestamp with time zone))
5. 0.000 0.000 ↓ 0.0

Index Scan using index_merge_requests_closing_issues_on_merge_request_id on merge_requests_closing_issues (cost=0.43..3.68 rows=1 width=8) (actual rows= loops=)

  • Index Cond: (merge_request_id = merge_requests.id)
6. 0.000 0.000 ↓ 0.0

Index Scan using index_issue_metrics on issue_metrics (cost=0.43..0.71 rows=1 width=12) (actual rows= loops=)

  • Index Cond: (issue_id = merge_requests_closing_issues.issue_id)