planner: use TxnCtx.InfoSchema to prevent schema inconsistency

[hawkingrei]

What problem does this PR solve?

Issue Number: ref #41622

close #49751

Problem Summary:

What changed and how does it work?

The result of sctx.GetInfoSchema().(infoschema.InfoSchema) is not stable if the caller side is not in a transaction && snapshot_ts is not set, it just get the latest InfoSchema:

tidb/pkg/session/session.go

Lines 4052 to 4074 in c20874e

	func (s *session) GetInfoSchema() sessionctx.InfoschemaMetaVersion {
	vars := s.GetSessionVars()
	var is infoschema.InfoSchema
	if snap, ok := vars.SnapshotInfoschema.(infoschema.InfoSchema); ok {
	logutil.BgLogger().Info("use snapshot schema", zap.Uint64("conn", vars.ConnectionID), zap.Int64("schemaVersion", snap.SchemaMetaVersion()))
	is = snap
	} else {
	vars.TxnCtxMu.Lock()
	if vars.TxnCtx != nil {
	if tmp, ok := vars.TxnCtx.InfoSchema.(infoschema.InfoSchema); ok {
	is = tmp
	}
	}
	vars.TxnCtxMu.Unlock()
	}
	if is == nil {
	is = domain.GetDomain(s).InfoSchema()
	}
	// Override the infoschema if the session has temporary table.
	return temptable.AttachLocalTemporaryTableInfoSchema(s, is)
	}

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.

planner: use TxnCtx.InfoSchema to prevent schema inconsistency

[codecov]

Codecov Report

Merging #49947 (d162acb) into master (d6aeaf0) will decrease coverage by 3.2670%.
Report is 3 commits behind head on master.
The diff coverage is 33.3333%.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #49947        +/-   ##
================================================
- Coverage   72.0575%   68.7906%   -3.2670%     
================================================
  Files          1437       1439         +2     
  Lines        345628     407669     +62041     
================================================
+ Hits         249051     280438     +31387     
- Misses        76506     108394     +31888     
+ Partials      20071      18837      -1234     

Flag	Coverage Δ
integration	43.8999% <33.3333%> (?)
unit	72.0374% <ø> (-0.0201%)	⬇️

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

Components	Coverage Δ
dumpling	56.3129% <ø> (ø)
parser	∅ <ø> (∅)
br	43.9542% <ø> (-7.4449%)	⬇️

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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 [qw4990,tiancaiamao]

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-01-02 02:12:18.270794267 +0000 UTC m=+2136629.308021189: ☑️ agreed by tiancaiamao.
• 2024-01-02 02:15:07.605770562 +0000 UTC m=+2136798.642997489: ☑️ agreed by qw4990.

[hawkingrei]

/hold

[hawkingrei]

/unhold

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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