----- Original Message -----
Robert Hodges <robert.hodges@continuent.com> writes:
What would be cool is something like a group transaction that other threads can join so that the commit becomes atomic. Most of the parallel load use cases I can think of don't require you to coordinate things like isolation because they are conflict free anyway--it's just atomic group commit.
Hm, I don't quite have this.
Given T1 and T2, there is a facility to ensure that T2 will commit no sooner than T1. But there is no facility to prevent T1 from commiting before T2.
(This is what was needed for parallel replication).
How does Galera handle this in its parallel apply threads? Especially the case below marked on MDEV-6676 T1: DELETE FROM t1 WHERE a=1 T2: INSERT INTO t1 SET a=1 -- -- Daniel Black, Engineer @ Open Query (http://openquery.com.au) Remote expertise & maintenance for MySQL/MariaDB server environments.