MDEV-35157 : wrong binlog timestamps on secondary nodes of a galera c… #3601
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…luster Problem was missing thd->set_time() before binlog event execution in wsrep_apply_events. Removed part of earlier commit 1363580 because it had nothing to do with VERSIONED tables. Note that this commit does not contain mtr-testcase because actual timestamps on binlog file depends the actual time when events are executed and how long their execution takes. e
janlindstrom
force-pushed
the
10.5-MDEV-35157
branch
from
a519346
to
8e07f6b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…luster
Description
Problem was missing thd->set_time() before binlog event execution in wsrep_apply_events.
Note that this commit does not contain mtr-testcase because actual timestamps on binlog file depends the actual time when events are executed and how long
their execution takes.
Release Notes
TODO: What should the release notes say about this change?
Include any changed system variables, status variables or behaviour. Optionally list any https://mariadb.com/kb/ pages that need changing.
How can this PR be tested?
TODO: modify the automated test suite to verify that the PR causes MariaDB to behave as intended.
Consult the documentation on "Writing good test cases".
If the changes are not amenable to automated testing, please explain why not and carefully describe how to test manually.
Basing the PR against the correct MariaDB version
mainbranch.PR quality check