maria:bb-10.3-MDEV-15447

Branch merges

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related charm recipes

4c3c038... by Larysa Sherepa on 2018-10-18

CTE tests

67f06ca... by Brauge on 2018-10-09

MDEV-17359 Concatenation operator || in like expression

981a810... by Marko Mäkelä on 2018-10-18

Merge 10.2 into 10.3

64d26ec... by Marko Mäkelä on 2018-10-18

Fix the Windows build

On Windows, a mismatch between TIMETPF ("%ld") and time_t would be reported.
Use "%ld" and long, like the code used to be.

22eb146... by Marko Mäkelä on 2018-10-18

Merge 10.2 into 10.3

3eaae09... by Marko Mäkelä on 2018-10-18

Extend the use of innodb_default_row_format.combinations

56de291... by Marko Mäkelä on 2018-10-18

Fix a merge error in commit 28f08d3753eb10a1393a63e6c581d43aad9f93b9

f454189... by Marko Mäkelä on 2018-10-17

Merge 10.2 into 10.3

2fa4ed0... by Marko Mäkelä on 2018-10-17

MDEV-17483 Insert on delete-marked record can wrongly inherit old values for instantly added column

row_ins_clust_index_entry_low(): Do not call dtuple_t::trim()
before row_ins_clust_index_entry_by_modify(), so that the values
of all columns will be available in row_upd_build_difference_binary().
If applicable, the tuple can be trimmed in btr_cur_optimistic_update()
or btr_cur_pessimistic_update(), which will be called by
row_ins_clust_index_entry_by_modify().

853a0a4... by Marko Mäkelä on 2018-10-17

MDEV-13564: Set innodb_safe_truncate=ON by default

The setting innodb_safe_truncate=ON reduces compatibility with older
versions of MariaDB and backup tools in two ways.

First, we will be writing TRX_UNDO_RENAME_TABLE records, which older
versions do not know about. These records could be misinterpreted if
a DDL transaction was recovered and would be rolled back.
Such rollback is only possible if the server was killed while
an incomplete DDL transaction was persisted. On transaction completion,
the insert_undo log pages would only be repurposed for new undo log
allocations, and their contents would not matter. So, older versions
will not have a problem with innodb_safe_truncate=ON if the server was
shut down cleanly.

Second, to prevent such recovery failure, innodb_safe_truncate=ON will
cause a modification of the redo log format identifier, which will
prevent older versions from starting up after a crash. MariaDB Server
versions older than 10.2.13 will refuse to start up altogether, even
after clean shutdown.

A server restart with innodb_safe_truncate=OFF will restore compatibility
with older server and backup versions.