Skip to content

the cascades xformed opeartor should derive their stats own #58905

@AilinKid

Description

@AilinKid

Enhancement

ref: #51664

Image

from the pic above, we could see that, the transformed join(physicalized as index join) converted from apply-rule in cascades, didn't show the correct est rows with the same plan generated from normal planner mode.

the reason is that: currently the new generated/xformed logical operator will inherit their source operator's stats(row count included), so even the new join has its own stats derive logic, it couldn't derive it's own stats again because the reuse mechanism.

Metadata

Metadata

Assignees

No one assigned

    Labels

    planner/cascadesissue/enhance/bug related to yamssig/plannerSIG: Plannertype/enhancementThe issue or PR belongs to an enhancement.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions