-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
*: fix a timezone data race which may cause wrong row data (#41146) #41183
*: fix a timezone data race which may cause wrong row data (#41146) #41183
Conversation
Signed-off-by: ti-chi-bot <[email protected]>
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
/hold high priority for trunk branch |
/unhold |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 06e8615
|
/retest |
This is an automated cherry-pick of #41146
Signed-off-by: wjhuang2016 [email protected]
What problem does this PR solve?
Issue Number: close #40710
Problem Summary:
As mentioned in #40710, changing the timezone in the statement context may cause data race in getColDefaultValue().
What is changed and how it works?
Add an explicit timezone argument instead of changing the timezone in the statement context.
Check List
Tests
Run the test mentioned in data race in TimeZone causes data-index inconsistency #40710. since this PR completely avoids this data race, there is no need to write a unit test. And the unit test for it is meaningless.
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.