Add Optional Invisible Primary Key to History for Replication in MySQL and MariaDB #586
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.
Pull Request adds an optional primary key for the history table which is needed for replication.
option mysql/maria_history_pk is added to the config/CLI.
Change will check that the InnoDB storage engine is being used and that the MySQL/MariaDB version is at a level that supports inivisible primary keys before adding one. If not it falls back to the default option.
Example change in table with and without.
When testing on an incompatible version
Message is reported the minimum supported version but continues anyway without the invisible PK.
This way it should allow adding the primary key for replication where it is needed, but also provide minimal disruption where it is not.
Same change in MySQL and MariaDB