server: ignore Preprocess error for the prefetchPointPlanKeys optimization

[tiancaiamao]

What problem does this PR solve?

Issue Number: close #39664

Problem Summary:

What is changed and how it works?

The error is throw from the Preprocess() in the prefetchPointPlanKeys.
prefetchPointPlanKeys is quite tricky, it does not reuse the common code path for the sake of performance.

Premature optimization is the root of all evil.
This tricky optimization helped us improve the performance by 100 times and won the deal, and now it's time to pay the (technical) debt.

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.

None

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• coocood
• lance6716

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.

[dveeden]

@jackysp @coocood looks like this PR is pending on your review?

[coocood]

What if there is some other kind of error we can not ignore?

[tiancaiamao]

What if there is some other kind of error we can not ignore?

If other kinds of error happen, we just bypass this optimization. Bypass this optimization is always safe.
Maybe the query would get error again when it execute later, whatever, it's safe to get the expected result and fix weird errors like #39664

@coocood

[tiancaiamao]

PTAL @jackysp

[tiancaiamao]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 194d26c

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-5.3: #43056.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-5.4: #43057.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.1: #43058.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.5: #43059.