mariadb

mirror of https://github.com/MariaDB/server.git synced 2025-12-01 17:39:21 +03:00

Files

Andrei Elkin 946a07e8a8 Fix for MDEV-9670 server_id mysteriously set to 0

Problem was that in a circular replication setup the master remembers
position to events it has generated itself when reading from a slave.
If there are no new events in the queue from the slave, a
Gtid_list_log_event is generated to remember the last skipped event.
The problem happens if there is a network delay and we generate a
Gtid_list_log_event in the middle of the transaction, in which case there
will be an implicit comment and a new transaction with serverid=0 will be
logged.

The fix was to not generate any Gtid_list_log_events in the middle of a
transaction.

2017-07-02 19:47:30 +03:00

extension

Change a couple of permissions that cause lintian warnings in .deb packaging and don't really hurt to fix.

2014-08-13 15:46:39 +02:00

include

MDEV-6926: innodb_rows_updated is misleading on slav

2014-10-26 07:22:51 +02:00

Fix for MDEV-9670 server_id mysteriously set to 0

2017-07-02 19:47:30 +03:00

Fix for MDEV-9670 server_id mysteriously set to 0

2017-07-02 19:47:30 +03:00

disabled.def

Bug#17638477 UNINSTALL AND INSTALL SEMI-SYNC PLUGIN CAUSES SLAVES TO BREAK

2014-08-03 12:45:14 +02:00

my.cnf

…

README

…

rpl_1slave_base.cnf

…

README

How to run.
===========

./mysql-test-run.pl --suite=rpl --mysqld=--binlog-format=mixed