Details
-
Type:
Task
-
Status: Stalled (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Fix Version/s: None
-
Component/s: Server
-
Labels:
Description
This issue was previously marked as a duplicate and it was opted to use last_gtid instead I believe. However this causes compatibility issues with ProxySQL for instance, which uses SESSION_TRACK_GTIDS to support causal reads as described here: https://proxysql.com/blog/proxysql-gtid-causal-reads/.
It might prevent someone from migrating from MySQL to MariaDB and cause the reverse instead.
Attachments
Issue Links
- relates to
-
MDEV-15170 Implement SESSION_TRACK_GTIDS
-
- Closed
-