Skip to content

opt, sql: support PlanGram matching in FK cascades #172275

Description

@michae2

FK cascades are planned and run after the main query as postqueries. We should provide a way to control FK cascade plans using PlanGram matching.

Some ideas on how to implement this:

  • we could add a dummy expression to the PlanGram language to indicate which part of the PlanGram is a FK cascade
  • or have a separate statement hint type for FK cascades
  • or add another field to the pin plan statement hint protobuf for FK cascade PlanGram(s)

Jira issue: CRDB-65487

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-plan-managementA-statement-hintStatement 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)T-sql-queriesSQL Queries Team

    Fields

    No fields configured for Feature.

    Projects

    Status
    Medium-term

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions