planner: add logical plan iterator inside a memo starting with a root group.

[AilinKid]

What problem does this PR solve?

Issue Number: ref #51664

Problem Summary:

What changed and how does it work?

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[tiprow]

Hi @AilinKid. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.5942%. Comparing base (dc4cb9b) to head (45b86fb).
Report is 14 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #58557        +/-   ##
================================================
+ Coverage   73.1264%   73.5942%   +0.4677%     
================================================
  Files          1676       1677         +1     
  Lines        463585     465572      +1987     
================================================
+ Hits         339003     342634      +3631     
+ Misses       103743     101987      -1756     
- Partials      20839      20951       +112     

Flag	Coverage Δ
integration	42.8369% <ø> (?)
unit	72.2881% <100.0000%> (-0.0350%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	52.6910% <ø> (ø)
parser	∅ <ø> (∅)
br	45.7945% <ø> (+0.0329%)	⬆️

[winoros]

The stack info is only used for debugging? Do we always need to operate it even if not in debugging mode?

[AilinKid]

it's for iter position record, one element for each group, when return a LP back, next iteration can start with this position rather than start from 0.

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-12-31 09:53:19.856390778 +0000 UTC m=+430535.212395310: ☑️ agreed by winoros.
• 2025-01-02 05:44:42.624359746 +0000 UTC m=+588417.980364285: ☑️ agreed by hawkingrei.

[hawkingrei]

/retest

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hawkingrei, winoros

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• pkg/planner/OWNERS [hawkingrei,winoros]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

@AilinKid: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
idc-jenkins-ci-tidb/check_dev	ad1f22c	link	true	/test check-dev

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.