maria:bb-10.2-andrei-ext

Last commit made on 2018-01-04
Get this branch:
git clone -b bb-10.2-andrei-ext https://git.launchpad.net/maria

Branch merges

Branch information

Name:
bb-10.2-andrei-ext
Repository:
lp:maria

Recent commits

d5a7c9d... by Andrei Elkin <email address hidden> on 2018-01-04

The slave io thread does not conduct integrity check for row-based
events. Specifically it tolerates missed STMT_END flag marked terminal
event that conclude a sequence of "elementary" "block" Rows-events.
Failure to react on a potentially missed event can confuse the applier thread
in various ways.

The slave io is made in this patch to track the STMT_END status.
Whenever at a first event following a sequence of Rows events the IO thread
finds out that a preceding Rows event did not actually had the flag, an
explicit error is issued.

Replication can be resumed as a provided test demonstrates.

Note that currently the row-based group integrity check is limited
to the version 1 rows event which are generated by Mariadb masters.

f7fd6ac... by Marko Mäkelä on 2018-01-03

Merge 10.2 into bb-10.2-ext

9eb3fcc... by Marko Mäkelä on 2018-01-03

Follow-up fix of MDEV-14717 RENAME TABLE in InnoDB is not crash-safe

trx_undo_page_report_rename(): Return a pointer to the start of the
undo log record, not to the start of the (not yet written) next free
record. The wrong return value would sometimes cause ROLLBACK to crash
in an assertion failure (trying to parse garbage from the free area at
the end of the insert_undo log page) if the TRX_UNDO_RENAME_TABLE record
was the very last thing that was written to the insert_undo log. This
would occasionally happen when an ALTER TABLE operation is rolled
back due to invalid FOREIGN KEY constraints in the innodb.innodb test.
In these tests, the error ER_ERROR_ON_RENAME (1025) would be returned
at the end of the ALGORITHM=COPY operation of ALTER TABLE.

d361401... by Marko Mäkelä on 2018-01-03

Merge 10.1 into 10.2, with some MDEV-14799 fixups

trx_undo_page_report_modify(): For SPATIAL INDEX, keep logging
updated off-page columns twice, so that
the minimum bounding rectangle (MBR) will be logged.
Avoiding the redundant logging would require larger changes
to the undo log format.

row_build_index_entry_low(): Handle SPATIAL_UNKNOWN more robustly,
by refusing to purge the record from the spatial index.
We can get this code when processing old undo log from 10.2.10 or
10.2.11 (the releases affected by MDEV-14799, which was a regression
from MDEV-14051).

7a9fee9... by Marko Mäkelä on 2018-01-02

MDEV-13568 gcol.innodb_virtual_debug_purge failed in buildbot with wrong result

The InnoDB background tasks can modify tables while LOCK TABLES...WRITE
is in effect. The purge of InnoDB history always worked like this in
MariaDB, but in MySQL 5.7 it sometimes yields to LOCK TABLES.

Also, make gcol.innodb_virtual_index run the purge for an UPDATE
before DROP TABLE is executed.

c2c2173... by Monty <email address hidden> on 2018-01-03

Merge remote-tracking branch 'origin/10.2' into bb-10.2-ext

16cd55a... by Monty <email address hidden> on 2018-01-02

Fixed crashing bug in mysqlbinlog

- The fix in mf_iocache2.c was just to fix a compiler warning

6f28f78... by Monty <email address hidden> on 2018-01-02

More output in galera.query_cache.test

This is to be able to better track where things goes wrong

83a8b0e... by Monty <email address hidden> on 2018-01-02

Fixed compiler warning

22b4f46... by Monty <email address hidden> on 2018-01-02

MDEV-14813 rpl.rpl_ctype_latin1 fails in buildbot on Mac with wrong result

Make rpl_ctype_latin1 more portable by printing names in hex
Also only run if lower_case_table_names is 0, as this affects the result