diff options
| author | unknown <knielsen@knielsen-hq.org> | 2013-07-10 12:01:52 +0200 |
|---|---|---|
| committer | unknown <knielsen@knielsen-hq.org> | 2013-07-10 12:01:52 +0200 |
| commit | 2f6a2494a5eb2cf3ab06fbedd2584eca85d90230 (patch) | |
| tree | 8d9d75502c8b64a769f3931f5801092392667b1d /mysql-test/r/lock_multi.result | |
| parent | 1e43277838581dfa5be2e755e524991cd7e2cebf (diff) | |
| download | mariadb-git-2f6a2494a5eb2cf3ab06fbedd2584eca85d90230.tar.gz | |
MDEV-4708: GTID strict mode doesn't work on a database with purged binlogs
When a new master is provisioned that does not have any old binlogs,
the @@gtid_slave_pos is used to know where in the GTID history the
provisioning happened. A slave is allowed to connect at the point of
this value of @@gtid_slave_pos, even if that GTID is not in the
binlogs on the new master.
The code to handle this case when the binlog on the newly provisioned
master is completely empty was just wrong (couple of typos). Clearly it
had never been tested ... :-/
Diffstat (limited to 'mysql-test/r/lock_multi.result')
0 files changed, 0 insertions, 0 deletions