Kristian Nielsen d632c85bb7 MDEV-31723: Crash on SET SESSION gtid_seq_no= DEFAULT ...

A simple "SET SESSION gtid_seq_no= DEFAULT" did not work, it would straight
up crash the server! Also, explicitly setting gtid_seq_no to 0 gave an error
in --gtid-strict-mode=1.

Setting to DEFAULT or 0 should disable any prior setting of
gtid_seq_no, so that the next transaction is allocated the next GTID
in sequence, as normal.

Reviewed-by: Monty <monty@mariadb.org>
Signed-off-by: Kristian Nielsen <knielsen@knielsen-hq.org>

2023-07-30 22:00:43 +02:00

..

inc

Fix all warnings given by UBSAN

2021-04-20 12:30:09 +03:00

r

MDEV-31723: Crash on SET SESSION gtid_seq_no= DEFAULT

2023-07-30 22:00:43 +02:00

t

MDEV-31723: Crash on SET SESSION gtid_seq_no= DEFAULT

2023-07-30 22:00:43 +02:00

disabled.def

…