8000 executor: fix query infoschema.tables table_schema/table_name with filter condition (#57746) by ti-chi-bot · Pull Request #57771 · pingcap/tidb · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

executor: fix query infoschema.tables table_schema/table_name with filter condition (#57746) #57771

Merged

Conversation

ti-chi-bot
Copy link
Member

This is an automated cherry-pick of #57746

What problem does this PR solve?

Issue Number: close #57657

Problem Summary:

What changed and how does it work?

There is a special optimize that if the result columns for query on INFORMATION_SCHEMA.TABLES only contains table_schema table_name, all the data are in-memory, then we have a special code path for such case #55574
But that code path differ from the main code path and miss some filter conditions, so it cause the bug in issue #57657

This fix will make the special optimize check more strick.
Only the queries for table_name table_schema columns AND WITHOUT OTHER FILTER CONDITIONS run to the special optimization.

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.

None

@ti-chi-bot ti-chi-bot added release-note-none Denotes a PR that doesn't merit a release note. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. type/cherry-pick-for-release-8.5 This PR is cherry-picked to release-8.5 from a source PR. labels Nov 27, 2024
Copy link
codecov bot commented Nov 27, 2024

Codecov Report

Attention: Patch coverage is 90.00000% with 1 line in your changes missing coverage. Please review.

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

Additional details and impacted files
@@               Coverage Diff                @@
##             release-8.5     #57771   +/-   ##
================================================
  Coverage               ?   57.2301%           
================================================
  Files                  ?       1770           
  Lines                  ?     628894           
  Branches               ?          0           
================================================
  Hits                   ?     359917           
  Misses                 ?     244939           
  Partials               ?      24038           
Flag Coverage Δ
integration 37.1958% <90.0000%> (?)
unit 72.9279% <90.0000%> (?)

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

Components Coverage Δ
dumpling 52.9478% <0.0000%> (?)
parser ∅ <0.0000%> (?)
br 52.3321% <0.0000%> (?)

@tiancaiamao tiancaiamao requested a review from tangenta November 28, 2024 07:41
@ti-chi-bot ti-chi-bot bot added approved needs-1-more-lgtm Indicates a PR needs 1 more LGTM. cherry-pick-approved Cherry pick PR approved by release team. and removed do-not-merge/cherry-pick-not-approved labels Nov 28, 2024
Copy link
ti-chi-bot bot commented Nov 28, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tangenta, 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 [tangenta,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 ti-chi-bot bot added lgtm and removed needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Nov 28, 2024
Copy link
ti-chi-bot bot commented Nov 28, 2024

[LGTM Timeline notifier]

Timeline:

  • 2024-11-28 08:01:19.383125998 +0000 UTC m=+709867.002780514: ☑️ agreed by tangenta.
  • 2024-11-28 13:21:41.258647811 +0000 UTC m=+729088.878302327: ☑️ agreed by tiancaiamao.

@jebter
Copy link
jebter commented Nov 29, 2024

/retest

< 8000 !-- -->

@ti-chi-bot ti-chi-bot bot merged commit bfa61d2 into pingcap:release-8.5 Nov 29, 2024
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved cherry-pick-approved Cherry pick PR approved by release team. lgtm release-note-none Denotes a PR that doesn't merit a release note. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. type/cherry-pick-for-release-8.5 This PR is cherry-picked to release-8.5 from a source PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants
0