Hi,

the GTID of the last transaction is exposed via the last_gtid session variable ([1]).

[1]: https://mariadb.com/kb/en/mariadb/gtid/#last_gtid

In a Binlog Server deployment ([2]), the binlog file and position is a GTID. So knowing the binlog file and position of the last transaction is as valuable as knowing the GTID of the last transaction.

[2]: https://blog.booking.com/abstracting_binlog_servers_and_mysql_master_promotion_wo_reconfig...

So please consider exposing the binlog file and position of the last transaction in a session variable.

Also please consider exposing that in at the protocol level in the OK packet (related to MDEV-11956).

Many thanks,

JFG