-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
statistics: try to keep the drop stats behavior unchanged #58307
base: master
Are you sure you want to change the base?
Conversation
Please add issue link. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #58307 +/- ##
================================================
+ Coverage 73.2226% 73.8622% +0.6396%
================================================
Files 1679 1709 +30
Lines 462548 471292 +8744
================================================
+ Hits 338690 348107 +9417
+ Misses 103086 101687 -1399
- Partials 20772 21498 +726
Flags with carried forward coverage won't be shown. Click here to find out more.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hawkingrei 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:
Approvers can indicate their approval by writing |
[LGTM Timeline notifier]Timeline:
|
What problem does this PR solve?
Issue Number: ref #57901, #58181
Problem Summary:
The first phase of the DROP STATS is the same with the case that the DDL event handler failed to handle the create table event:
To keep the second case(DDL failed to handle the create table event, but the table should have stats) behavior correct and to make the DROP STATS not affected by the changes, this pull request changes the code to ease the problem.
What changed and how does it work?
This pull request tries to make a few changes to make sure that auto-analyze will not be triggered after the DROP STATS happen.
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.