Null merge 5.5.48 to 5.6.29 #384
Merged
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
The tests for 74644, 77832, 74783, 75701, 74580 are added. 74783 test is not added as 5.5 innodb does not support fulltext indexes. Conflicts: VERSION mysql-test/r/mysql_plugin.result sql/sql_reload.cc sql/sql_select.cc
Merge 5.5.47
Fix bug 1530102 (rpl.rpl_bug68490 fails under Valgrind in Jenkins)
…na-server into hrvojem-rn-5.5.47-37.7-5.5
Merge branch 'hrvojem-rn-5.5.47-37.7-5.5' into 5.5
Release 5.5.47-37.7
…6-ctype_ucs Fix bug lp:1534246 (5.5) "'ctype_ucs.test' fails sporadically"
Fix bug 1233431 ([ERROR] Cannot find index <col> in InnoDB index tran…
5.5 - Changed package name for cpack from mysql to percona-server (BLD-309)
5.5 - Fix for custom socket location on centos 7 (#1534825)
Fixed LP bug #1521481 by adding a know issues section
5.5 - Add --skip-log-bin for bootstrap mode and run mysql_install_db only on upgrade in debian
vlad-lesin
force-pushed
the
null-merge-5.5.48-to-5.6.29
branch
from
c205564
to
176d2c4
Compare
|
LGTM |
vlad-lesin
pushed a commit
that referenced
this pull request
Mar 2, 2016
Null merge 5.5.48 to 5.6.29
inikep
pushed a commit
to inikep/percona-server
that referenced
this pull request
Apr 23, 2020
Summary: Currently to ensure crash safety in slave a DB->GTID map is maintained which is updated after every commit. The map is required to identify holes in the sequence of gtids caused by using MTS. In RBR we can make use of idempotency of row events to handle holes instead. We only track the max gtid encountered and after a crash we turn on idempotency for all transactions which have gtid less than the max gtid. If any trx was already executed in this range it's okay because we've turned on idempotent mode. Closes facebook/mysql-5.6#384 Differential Revision: D4113718 Pulled By: abhinav04sharma fbshipit-source-id: 4c6da14 fbshipit-source-id: 253c185fc6c
inikep
pushed a commit
to inikep/percona-server
that referenced
this pull request
Feb 24, 2021
Summary: Currently to ensure crash safety in slave a DB->GTID map is maintained which is updated after every commit. The map is required to identify holes in the sequence of gtids caused by using MTS. In RBR we can make use of idempotency of row events to handle holes instead. We only track the max gtid encountered and after a crash we turn on idempotency for all transactions which have gtid less than the max gtid. If any trx was already executed in this range it's okay because we've turned on idempotent mode. Closes facebook/mysql-5.6#384 Differential Revision: D4113718 Pulled By: abhinav04sharma
inikep
pushed a commit
to inikep/percona-server
that referenced
this pull request
Nov 15, 2021
…#384) Summary: Currently to ensure crash safety in slave a DB->GTID map is maintained which is updated after every commit. The map is required to identify holes in the sequence of gtids caused by using MTS. In RBR we can make use of idempotency of row events to handle holes instead. We only track the max gtid encountered and after a crash we turn on idempotency for all transactions which have gtid less than the max gtid. If any trx was already executed in this range it's okay because we've turned on idempotent mode. Closes facebook/mysql-5.6#384 Differential Revision: D4113718 (facebook/mysql-5.6@74c27d7) Pulled By: abhinav04sharma fbshipit-source-id: 6471d74198a
ldonoso
pushed a commit
to ldonoso/percona-server
that referenced
this pull request
Mar 15, 2022
…#384) Summary: Currently to ensure crash safety in slave a DB->GTID map is maintained which is updated after every commit. The map is required to identify holes in the sequence of gtids caused by using MTS. In RBR we can make use of idempotency of row events to handle holes instead. We only track the max gtid encountered and after a crash we turn on idempotency for all transactions which have gtid less than the max gtid. If any trx was already executed in this range it's okay because we've turned on idempotent mode. Closes facebook/mysql-5.6#384 Differential Revision: D4113718 Pulled By: abhinav04sharma
inikep
pushed a commit
to inikep/percona-server
that referenced
this pull request
Apr 9, 2024
…#384) Summary: Currently to ensure crash safety in slave a DB->GTID map is maintained which is updated after every commit. The map is required to identify holes in the sequence of gtids caused by using MTS. In RBR we can make use of idempotency of row events to handle holes instead. We only track the max gtid encountered and after a crash we turn on idempotency for all transactions which have gtid less than the max gtid. If any trx was already executed in this range it's okay because we've turned on idempotent mode. Closes facebook/mysql-5.6#384 Differential Revision: D4113718 Pulled By: abhinav04sharma
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.
Null merge 5.5.48 to 5.6.29