Details
-
Task
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Duplicate
-
None
Description
Hi,
the GTID of the last transaction is exposed via the last_gtid session variable ([1]). This needs a round-trip to the server, which could be unwanted in some situations.
[1]: https://mariadb.com/kb/en/mariadb/gtid/#last_gtid
Upstream MySQL implements a way to get the GTID of the last transaction at the protocol level in the OK packet. ([2], [3] and [4]). I think this would be a good feature in MariaDB Server.
[2]: https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_session_track_gtids
[3]: https://dev.mysql.com/doc/refman/5.7/en/mysql-session-track-get-first.html
[4]: https://dev.mysql.com/doc/refman/5.7/en/mysql-session-track-get-next.html
Please also consider this improvement on the upstream implementation: Request transaction GTID in OK packet on COMMIT(without needing a round-trip) - [5].
[5]: https://bugs.mysql.com/bug.php?id=84748
Many thanks,
JFG
Attachments
Issue Links
- blocks
-
MXS-1778 Consistent reads by the utlization of GTID in OK packet.
- Closed
- duplicates
-
MDEV-15170 Implement SESSION_TRACK_GTIDS
- Closed
-
MDEV-15477 SESSION_SYSVARS_TRACKER does not track last_gtid
- Closed
- relates to
-
MDEV-15477 SESSION_SYSVARS_TRACKER does not track last_gtid
- Closed
-
CONC-302 SESSION_TRACK_GTIDS not implemented
- Closed