maria:bb-10.3-MDEV-27691

Last commit made on 2022-06-27
Get this branch:
git clone -b bb-10.3-MDEV-27691 https://git.launchpad.net/maria

Branch merges

Branch information

Name:
bb-10.3-MDEV-27691
Repository:
lp:maria

Recent commits

85b0d13... by Oleksandr "Sanja" Byelkin

MDEV-27691: post probe to disable service connection

ef55632... by Lena Startseva <email address hidden>

MDEV-27691: make working view-protocol

Fixed failed tests

866cd2e... by Lena Startseva <email address hidden>

MDEV-27691: make working view-protocol

Fixed failed tests

caac25f... by Lena Startseva <email address hidden>

MDEV-27691: make working view-protocol

Test with checking metadata or that do not allow to use util connection
for view-protocol are excluded from --view-protocol.
Also cases with bugs for --view-protocol are disabled.

1625a9a... by Oleksandr "Sanja" Byelkin

MDEV-27691: prequisite enable/disable service connection

b208030... by Marko Mäkelä

MDEV-11415 merge fixup: Remove a redundant call

In merge commit 921c5e931452301a09c84c53ffe35b81e6a1c71a the call
log_free_check() was accidentally duplicated, causing a small
performance regression on INSERT.

9286c9e... by midenok

MDEV-28254 Wrong position for row_start, row_end after adding column to implicit versioned table

Implicit system-versioned table does not contain system fields in SHOW
CREATE. Therefore after mysqldump recovery such table has system
fields in the last place in frm image. The original table meanwhile
does not guarantee these system fields on last place because adding
new fields via ALTER TABLE places them last. Thus the order of fields
may be different between master and slave, so row-based replication
may fail.

To fix this on ALTER TABLE we now place system-invisible fields always
last in frm image. If the table was created via old revision and has
an incorrect order of fields it can be fixed via any copy operation of
ALTER TABLE, f.ex.:

  ALTER TABLE t1 FORCE;

To check the order of fields in frm file one can use hexdump:

  hexdump -C t1.frm

Note, the replication fails only when all 3 conditions are met:

  1. row-based or mixed mode replication;
  2. table has new fields added via ALTER TABLE;
  3. table was rebuilt on some, but not all nodes via mysqldump image.

Otherwise it will operate properly even with incorrect order of
fields.

88a9f13... by midenok

MDEV-25546 LIMIT partitioning does not respect ROLLBACK

vers_info->hist_part retained stale value after ROLLBACK. The
algorithm in vers_set_hist_part() continued iteration from that value.

The simplest solution is to process partitions each time from start
for LIMIT in vers_set_hist_part().

4d11290... by Sergei Golubchik

.gitignore

6f6c74b... by Sergei Golubchik

Merge branch '10.2' into 10.3