Details
-
Task
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
Description
In MariaDB the UNTIL keyword is inclusive.
"The replica will start replication from the current GTID position, run up to and including the event with the GTID specified, and then stop. "
https://mariadb.com/kb/en/gtid/#start-slave-until-master_gtid_posxxx
Keyword UNTIL origin is form imperative languages, where UNTIL is the end condition of a loop.
Depending from the position of the counter (before or after reply), the UNTIL condition will be processed or not.
SQL is a declarative language, so the counter position in the loop is hidden, so maybe UNTIL is different implemented in different databases (if used in an SQL-statement, not procedures). Procedures are also based on imperative paradigm.
So I suggest to add keywords EXCLUSIVE and INCLUSIVE.
The default would be INCLUSIVE, which is the current MariaDB behaviour.
Example:
START SLAVE UNTIL EXCLUSIVE master_gtid_pos = <GTID position>;
|
Attachments
Issue Links
- causes
-
MDEV-32184 rpl.rpl_gtid_until_before_after_gtids regularly times out
-
- Closed
-
- is blocked by
-
-
- Closed
-
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Activity
| Transition | Time In Source Status | Execution Times |
|---|
|
65d 23h 22m | 1 |
|
1h 49m | 1 |
|
533d 8h 9m | 1 |
|
19d 14h 21m | 1 |
|
18d 4h 57m | 1 |
|
2h 41m | 1 |
|
41d 8h 49m | 1 |
|
11h 20m | 1 |