File: MDEV-35281.test

package info (click to toggle)
mariadb 1%3A11.8.2-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, trixie
  • size: 765,428 kB
  • sloc: ansic: 2,382,827; cpp: 1,803,532; asm: 378,315; perl: 63,176; sh: 46,496; pascal: 40,776; java: 39,363; yacc: 20,428; python: 19,506; sql: 17,864; xml: 12,463; ruby: 8,544; makefile: 6,059; cs: 5,855; ada: 1,700; lex: 1,193; javascript: 1,039; objc: 80; tcl: 73; awk: 46; php: 22
file content (37 lines) | stat: -rw-r--r-- 1,367 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
#
# MDEV-35281 - SR transaction crashes with innodb_snapshot_isolation
#
# Test outline: a simple SR transaction fails to remove
# its fragments from streaming_log table, with error
# HA_ERR_RECORD_CHANGED.
# This happens with the following sequence of events:
# 1. Start a streaming replication transaction
# 2. The transaction creates a read view in InnoDB
#    (this must happen before a fragment is replicated)
# 3. The transaction replicates a fragment.
#    Internally, a new transaction is created to INSERT
#    a row representing the fragment into the streaming_log
#    table and is committed immediately.
# 4. The streaming replication transaction COMMITs.
#    Before committing, the transaction replicates
#    a commit fragment and DELETEs its fragments that
#    were created in the streaming_log table.
#    If bug is present, fragment removal from the
#    streaming_log table violates snapshot isolation,
#    thus the operation fails with HA_ERR_RECORD_CHANGED.
#    (One or more records from the streaming_log table
#    are removed, while these were not visible to
#    the transaction).

--source include/galera_cluster.inc

CREATE TABLE t1 (f1 INTEGER PRIMARY KEY);

SET SESSION wsrep_trx_fragment_size=1;
SET SESSION innodb_snapshot_isolation=ON;

START TRANSACTION WITH CONSISTENT SNAPSHOT;
INSERT INTO t1 VALUES (1);
COMMIT;

DROP TABLE t1;