Last commit made on 2019-06-13
Get this branch:
git clone -b nm/mtr-force-doc

Branch merges

Branch information


Recent commits

fc4aaff... by Nikita Malyavin on 2019-06-13

mysql-test-run: mention --force in --max-test-fail description

06be8cd... by Marko Mäkelä on 2019-06-12

Clean up the test innodb.innodb-64k-crash

Before killing the server, ensure that the incomplete state of
the transaction will be made durable and will be applied and
rolled back on recovery, so that each time, roughly the same
amount of work will be done.

Remove DML statements after the recovery, and execute
CHECK TABLE instead.

1d31bed... by Marko Mäkelä on 2019-06-12

Merge 10.1 into 10.2

56c60b2... by Marko Mäkelä on 2019-06-12

MDEV-16111 encryption.innodb_lotoftables failed in buildbot with wrong result

Remove the test, because it easily fails with a result difference.
Analysis by Thirunarayanan Balathandayuthapani:

By default, innodb_encrypt_tables=0.
1) Test case creates 100 tables in innodb_encrypt_1.
2) creates another 100 unencrypted tables (encryption=off) in innodb_encrypt_2
3) creates another 100 encrypted tables (encryption=on) in innodb_encrypt_3
4) enabling innodb_encrypt_tables=1 and checking that only
100 encrypted tables exist. (already we have 100 in dictionary)
5) opening all tables again (no idea why)
6) After that, set innodb_encrypt_tables=0 and wait for 100 tables
to be decrypted (already we have 100 unencrypted tables)
7) dropping all databases

Sporadic failure happens because after step 4, it could encrypt the
normal table too, because innodb_encryption_threads=4.

This test was added in MDEV-9931, which was about InnoDB startup being
slow due to all .ibd files being opened. There have been a number of
later fixes to this problem. Currently the latest one is
commit cad56fbabaea7b5dab0ccfbabb98d0a9c61f3dc3, in which some tests
(in particular the test innodb.alter_kill) could fail if all InnoDB
.ibd files are read during startup. That could make this test redundant.

Let us remove the test, because it is big, slow, unreliable, and
does not seem to reliably catch the problem that all files are being
read on InnoDB startup.

90fec96... by Marko Mäkelä on 2019-06-12

Merge 10.1 into 10.2

94e6655... by Marko Mäkelä on 2019-06-12

MDEV-19740: Remove some broken InnoDB systemd code

GCC 9.1.1 noticed that sd_notifyf() was always being invoked with
str=NULL argument for "%s". This code was added in
commit 2e814d4702d71a04388386a9f591d14a35980bfe
but not mentioned in the commit comment.

The STATUS messages for systemd matter during startup and shutdown,
and should not be emitted during normal operation.

ib_senderrf(): Remove the potentially harmful sd_notifyf() calls.

efc3cb9... by sjaakola <email address hidden> on 2019-06-12

MDEV-19563 Removed references to deprecated option innodb_locks_unsafe_for_binlog

innodb_locks_unsafe_for_binlog variabe removed from wsrep_info test configuration and
recommendation to use this variable in README-wsrep was removed as well

Also relates to issue: MDEV-19544

9d886de... by Sergey Vojtovich on 2019-06-12

MDEV-16467 - MariaDB crashes because of "long semaphore wait"after migrating from 10.1 to 10.3

This patch fixes 10.2 issue reported in MDEV-16467 by partial backport of
c2118a0. Specifically "Remove not needed LOCK_thread_count from

4bbd8be... by Marko Mäkelä on 2019-06-12

Merge 10.1 into 10.2

b2f76ba... by Thirunarayanan Balathandayuthapani <email address hidden> on 2019-06-12

MDEV-16866 InnoDB fails to start upon crash recovery with "[ERROR] InnoDB: Redo log crypto: failed to decrypt log block"

- Post-push fix to change the copyright of both xtradb and innodb file.