sql: fix statement bug

[TomShawn]

What is changed, added or deleted? (Required)

sql: fix statement bug

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions.

• master (the latest development version)
• v6.6 (TiDB 6.6 versions)
• v6.5 (TiDB 6.5 versions)
• v6.4 (TiDB 6.4 versions)
• v6.1 (TiDB 6.1 versions)
• v5.4 (TiDB 5.4 versions)
• v5.3 (TiDB 5.3 versions)
• v5.2 (TiDB 5.2 versions)
• v5.1 (TiDB 5.1 versions)
• v5.0 (TiDB 5.0 versions)

What is the related PR or file link(s)?

• This PR is translated from:
• Other reference link(s):

Do your changes match any of the following descriptions?

• Delete files
• Change aliases
• Need modification after applied to another branch
• Might cause conflicts after applied to another branch

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• Oreoxmt
• tangenta

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.

[Oreoxmt]

LGTM

[djshow832]

Why not apply to older versions? I saw that the doc of 5.4 is also wrong.

[TomShawn]

Why not apply to older versions? I saw that the doc of 5.4 is also wrong.

Because the number of versions is growing very fast, so is the number of branches to cherry-pick. It is not economical to update all applicable versions. So we only update the latest few versions by default (including the latest LTS and DMR) unless someone (from customer feedback) asks for the update of older versions. Then it will be handled on-demand.

[TomShawn]

/merge

[ti-chi-bot]

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

Commit hash: 81edc59

[ti-chi-bot]

In response to a cherrypick label: new pull request created: #11566.

[ti-chi-bot]

In response to a cherrypick label: new pull request created: #11567.