planner, store/copr: allow limit on range partitioned table

[you06]

Signed-off-by: you06 you1474600@gmail.com

What problem does this PR solve?

Issue Number: ref #41480

Problem Summary:

Currently we when there is order by xx limit n statement over a partitioned table, and the xx is the partitioned PK, we still use a TopN plan which read across all related partitions, but there is a chance to stop earlier when the partition type is range.

What is changed and how it works?

Use a limit plan when the table is range partitioned.

Check List

Tests

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

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.

Support limit on range partitioned table, which speeds up limit-n statements.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has not been approved.

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

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

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[hawkingrei]

/retest

[you06]

It's not unstable, the test need to be fixed due to this PR's update.

[ti-chi-bot]

@you06: PR needs rebase.

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/test-infra repository.

[tiancaiamao]

What if the partition key is not the row id key?

[tiancaiamao]

table schema:
primary key a
partition by b

query:
order by b limit
order by a limit

[ti-chi-bot]

@you06: The following tests 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/mysql-test	7f4fe22	link	true	/test mysql-test
pull-integration-ddl-test	7f4fe22	link	true	/test pull-integration-ddl-test
pull-mysql-client-test	7f4fe22	link	true	/test pull-mysql-client-test
idc-jenkins-ci-tidb/unit-test	7f4fe22	link	true	/test unit-test
idc-jenkins-ci-tidb/check_dev_2	7f4fe22	link	true	/test check-dev2
idc-jenkins-ci-tidb/check_dev	7f4fe22	link	true	/test check-dev
idc-jenkins-ci-tidb/build	7f4fe22	link	true	/test build
pull-br-integration-test	7f4fe22	link	true	/test pull-br-integration-test
pull-lightning-integration-test	7f4fe22	link	true	/test pull-lightning-integration-test

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/test-infra repository. I understand the commands that are listed here.