You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A GTID is represented as a pair of coordinates, separated by a colon character (:), as shown here:
GTID = source_id:transaction_id
...
MySQL 8.4 also supports tagged GTIDs. A tagged GTID consists of three parts, separated by colon characters, as shown here:
GTID = source_id:tag:transaction_id
ProxySQL's behavior is currently undefined and needs to be investigated.
ProxySQL version
All the versions to the latest (2.7.0)
OS version
All
The steps to reproduce the issue
It should be enough to configure ProxySQL to process GTIDs, and on the backend enable tags in GTIDs.
This issue is to report an incompatibility issue with MySQL 8.4+ if GTID is used with tags.
From https://dev.mysql.com/doc/refman/8.4/en/replication-gtids-concepts.html :
ProxySQL's behavior is currently undefined and needs to be investigated.
All the versions to the latest (2.7.0)
All
It should be enough to configure ProxySQL to process GTIDs, and on the backend enable tags in GTIDs.
Note: this affects also the binlog reader: https://github.com/sysown/proxysql_mysqlbinlog
The text was updated successfully, but these errors were encountered: