executor: make TestOrderByAndLimit stable

[Defined2014]

What problem does this PR solve?

Issue Number: close #45496

Problem Summary:

The test easy failed when `limit = 1`.

Like `select /*+ LIMIT_TO_COP() */ * from tlist use index(idx_b) where b > 1126 and b < greatest(1127+1, 1127) order by b limit 1`.

It will change to `b = 1127`. Sometimes we have more than 1 line equal to 1127, so the result is unstable.

What is changed and how it works?

Check List

Tests

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

Modify y=1 to run the test without error.

• 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.

None

[tiprow]

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

[Defined2014]

/test check-issue-triage-complete

[ti-chi-bot]

@Defined2014: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test build
• /test canary-scan-security
• /test check-dev
• /test check-dev2
• /test mysql-test
• /test pingcap/tidb/canary_ghpr_unit_test
• /test pull-br-integration-test
• /test pull-common-test
• /test pull-e2e-test
• /test pull-integration-common-test
• /test pull-integration-copr-test
• /test pull-integration-ddl-test
• /test pull-integration-jdbc-test
• /test pull-integration-mysql-test
• /test pull-sqllogic-test
• /test pull-tiflash-test
• /test unit-test

The following commands are available to trigger optional jobs:

• /test pull-notify-when-compatibility-sections-changed

Use /test all to run the following jobs that were automatically triggered:

• pingcap/tidb/ghpr_build
• pingcap/tidb/ghpr_check
• pingcap/tidb/ghpr_check2
• pingcap/tidb/ghpr_mysql_test
• pingcap/tidb/ghpr_unit_test

In response to this:

/test check-issue-triage-complete

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.

[Defined2014]

/run check-issue-triage-complete

[tiprow]

@Defined2014: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test check-issue-triage-complete

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.

[hawkingrei]

/check-issue-triage-complete
/ok-to-test

[codecov]

Codecov Report

Merging #45513 (30d3364) into master (9e20208) will increase coverage by 0.0025%.
The diff coverage is n/a.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #45513        +/-   ##
================================================
+ Coverage   73.2546%   73.2571%   +0.0024%     
================================================
  Files          1264       1267         +3     
  Lines        389252     389924       +672     
================================================
+ Hits         285145     285647       +502     
- Misses        85825      85961       +136     
- Partials      18282      18316        +34     

Flag	Coverage Δ
integration	78.1388% <ø> (?)
unit	73.2486% <ø> (-0.0060%)	⬇️

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

Components	Coverage Δ
dumpling	54.0444% <ø> (ø)
parser	85.0554% <ø> (ø)
br	52.0967% <ø> (-0.0506%)	⬇️

[Defined2014]

/test check_dev

[ti-chi-bot]

@Defined2014: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test build
• /test canary-scan-security
• /test check-dev
• /test check-dev2
• /test mysql-test
• /test pingcap/tidb/canary_ghpr_unit_test
• /test pull-br-integration-test
• /test pull-common-test
• /test pull-e2e-test
• /test pull-integration-common-test
• /test pull-integration-copr-test
• /test pull-integration-ddl-test
• /test pull-integration-jdbc-test
• /test pull-integration-mysql-test
• /test pull-sqllogic-test
• /test pull-tiflash-test
• /test unit-test

The following commands are available to trigger optional jobs:

• /test pull-notify-when-compatibility-sections-changed

Use /test all to run the following jobs that were automatically triggered:

• pingcap/tidb/ghpr_build
• pingcap/tidb/ghpr_check
• pingcap/tidb/ghpr_check2
• pingcap/tidb/ghpr_mysql_test
• pingcap/tidb/ghpr_unit_test

In response to this:

/test check_dev

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.

[Defined2014]

/test check-dev

[tiprow]

@Defined2014: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test tiprow_fast_test

In response to this:

/test check_dev

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.

[tiprow]

@Defined2014: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test tiprow_fast_test

In response to this:

/test check-dev

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.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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:

• OWNERS [hawkingrei,xhebox]

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]

[LGTM Timeline notifier]

Timeline:

• 2023-07-24 05:07:18.267257835 +0000 UTC m=+158180.861788839: ☑️ agreed by hawkingrei.
• 2023-07-24 05:15:40.978712869 +0000 UTC m=+158683.573243842: ☑️ agreed by xhebox.