yugabyte/yugabyte-db

Optimizer is picking a remote Index Scan for point lookup over a local Index Only Scan

Open

#17,654 opened on Jun 1, 2023

View on GitHub
 (0 comments) (0 reactions) (1 assignee)C (1,003 forks)batch import
good first issuejira-originatedkind/enhancementpriority/medium

Repository metrics

Stars
 (8,229 stars)
PR merge metrics
 (Avg merge 17d 21h) (92 merged PRs in 30d)

Description

Jira Link: DB-6772

Contributor guide

Research direction
Investigate why the query optimizer chooses a remote index scan over a local index only scan for point lookups. Examine the cost model and distributed query planning logic.
Tech stack
cpostgresql
Domain
backenddatabaseperformance
Issue type
Performance
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitCSQL
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30