planner: fix incorrectly using the schema for plan cache (#57964)

[ti-chi-bot]

This is an automated cherry-pick of #57964

What problem does this PR solve?

Issue Number: close #56733

Problem Summary:
If the table ID is changed for a given table name, the plan cache key is not updated.
For an insert statement, it may use the outdated schema, resulting in incorrect data or query results.

What changed and how does it work?

Make sure the tbl is updated in function planCachePreprocess() if tableByID doesn't return the table info.

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.

fix incorrectly using the schema for plan cache

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qw4990, tangenta

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/ddl/OWNERS [tangenta]
• pkg/planner/OWNERS [qw4990]

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:

• 2024-12-09 11:19:31.48287976 +0000 UTC m=+264561.571682298: ☑️ agreed by tangenta.
• 2024-12-09 12:17:45.666770029 +0000 UTC m=+268055.755572568: ☑️ agreed by qw4990.

[codecov]

Codecov Report

Attention: Patch coverage is 50.00000% with 3 lines in your changes missing coverage. Please review.

Please upload report for BASE (release-8.5@9db025d). Learn more about missing BASE report.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-8.5     #58090   +/-   ##
================================================
  Coverage               ?   57.1328%           
================================================
  Files                  ?       1773           
  Lines                  ?     629183           
  Branches               ?          0           
================================================
  Hits                   ?     359470           
  Misses                 ?     245576           
  Partials               ?      24137           

Flag	Coverage Δ
integration	37.1135% <50.0000%> (?)
unit	72.7856% <50.0000%> (?)

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

Components	Coverage Δ
dumpling	52.8711% <0.0000%> (?)
parser	∅ <0.0000%> (?)
br	52.5070% <0.0000%> (?)

[wuhuizuo]

/test all

[tiprow]

@wuhuizuo: No presubmit jobs available for pingcap/[email protected]

In response to this:

/test all

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.