Skip to content

statistics: skip build statistics for view in auto analyze#27866

Merged
ti-chi-bot merged 4 commits intopingcap:masterfrom
tiancaiamao:statistic-skip-view
Sep 8, 2021
Merged

statistics: skip build statistics for view in auto analyze#27866
ti-chi-bot merged 4 commits intopingcap:masterfrom
tiancaiamao:statistic-skip-view

Conversation

@tiancaiamao
Copy link
Contributor

What problem does this PR solve?

Issue Number: close #27274

I'm not sure will it also close #25898 and #26539, because in those two, the data race stack is lost.
After this fix, if we don't see them in the future, that means they are also fixed.

Problem Summary:

The DATA RACE happen between explain view (or "select * from information_schema.columns") and auto-analyze.

Auto analyze need to read the table column info, while 'explain view' will modify it.
tryFillViewColumnType will modify the column in model.TableInfo, It's not a operation on a copy of data.
This operation is dangerous.

What is changed and how it works?

What's Changed:

View is a special table, it doesn't not need to maintain the statistics.
This commit skip build statistics for view.

How it Works:

Statistics will skip the view table, so it doesn't conflict with the explain view or select * from infoschema.columns ...

Maybe change the tryFillViewColumnType function is another option, but this fix is obviously right, and just one line change.

Check List

Tests

  • Unit test
  • Integration test
  • Manual test (add detailed scripts or steps below)
  • No code

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

None

@ti-chi-bot
Copy link
Member

ti-chi-bot commented Sep 7, 2021

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • lzmhhh123
  • wjhuang2016

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.

Details

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

@ti-chi-bot ti-chi-bot added release-note-none Denotes a PR that doesn't merit a release note. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Sep 7, 2021
@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label Sep 7, 2021
@ti-chi-bot ti-chi-bot added status/LGT2 Indicates that a PR has LGTM 2. and removed status/LGT1 Indicates that a PR has LGTM 1. labels Sep 8, 2021
@lzmhhh123
Copy link
Contributor

@tiancaiamao does this pr need to cherry-pick?

@tiancaiamao
Copy link
Contributor Author

/merge

@ti-chi-bot
Copy link
Member

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

DetailsCommit hash: 8cc46ae

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Sep 8, 2021
@tiancaiamao
Copy link
Contributor Author

/merge

@tiancaiamao
Copy link
Contributor Author

/run-check_dev_2

@ti-chi-bot
Copy link
Member

@tiancaiamao: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

Details

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 ti-community-infra/tichi repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release-note-none Denotes a PR that doesn't merit a release note. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

data race detected in the test data race in tidb/domain/domain.go:1336

4 participants