-
Notifications
You must be signed in to change notification settings - Fork 4.1k
sql: add statement hint and builtin for plan pinning using PlanGram #170692
Copy link
Copy link
Open
Labels
A-plan-managementA-statement-hintStatement hints applied to queries externally from the statement_hints table.Statement hints applied to queries externally from the statement_hints table.C-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)T-sql-queriesSQL Queries TeamSQL Queries Team
Metadata
Metadata
Assignees
Labels
A-plan-managementA-statement-hintStatement hints applied to queries externally from the statement_hints table.Statement hints applied to queries externally from the statement_hints table.C-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)T-sql-queriesSQL Queries TeamSQL Queries Team
Type
Fields
Give feedbackNo fields configured for Feature.
Projects
Status
Triage
Similar to #170360, we should add a statement hint and a builtin (or extend the ones added for #170360) to support plan pinning using PlanGrams instead of plan gists. This will allow us to better test PlanGram matching in the optimizer.
Jira issue: CRDB-64121