14 Commits (872479aebae81bf7b4505477c7857786554c39aa)

Author	SHA1	Message	Date
Wazir Ahmed	04b258e80b	gtid: Add `NULL` check after `strchr()`	1 month ago
Rene Cannao	dca01d4eaf	Add I3/I4 message types for GTID range updates, disconnect on unknown message ... I1/I2 now strictly handle single trxid values (parsed via atoll). New I3/I4 messages handle range-based trxid updates (parsed as TrxId_Interval strings). This ensures backwards compatibility: an old ProxySQL receiving I3/I4 will safely ignore them via default:break, while a new ProxySQL correctly distinguishes single vs range messages. Also fixes events_read being incremented for unrecognized message types, and disconnects on unknown message types instead of silently ignoring them.	2 months ago
Wazir Ahmed	adec09b25a	chore(gtid): use consistent naming and remove unused code ... Signed-off-by: Wazir Ahmed <wazir@proxysql.com>	2 months ago
Lisandro Pin	96f1b44412	Parse GTID ranges on proxysql_mysqlbinlog update messages. ... This PR adds full support for ranges in `proxysql_mysqlbinlog` update messages, while also improving efficiency when dealing with GTID gaps for any given UUID. Single GTID updates are transparently supported, so older `proxysql_mysqlbinlog` version will continue to work with newer ProxySQL releases. See https://github.com/sysown/proxysql_mysqlbinlog/issues/33 for details.	2 months ago
Lisandro Pin	23c153f9d3	Add logic to support ranged GTID updates from proxysql_mysqlbinlog.	5 months ago
Rene Cannao	9a55e97429	docs: Add comprehensive Doxygen documentation for GTID refactoring ... - Document addGtidInterval() function with parameter details and reconnection behavior - Add documentation for readall() method explaining robust error handling - Document connect_cb() and reader_cb() callbacks with resource management details - Document generate_mysql_gtid_executed_tables() with multi-phase process explanation - Focus on functionality, thread safety, and performance improvements - Provide clear parameter descriptions and return value semantics	6 months ago
Wazir Ahmed	50c60284e6	gtid: Refactor reconnect logic & prevent `events_count` reset ... - This patch was originally added by commit 0a70fd5 and reverted by 8d1b5b5, prior to the release of `v3.0.3`. - The following issues are addressed in this update, - Fix for `use-after-free` issue which occured during CI test. - Fix for deadlock issue between `GTID_syncer` and `MySQL_Worker`. Signed-off-by: Wazir Ahmed <wazir@proxysql.com>	6 months ago
Wazir Ahmed	8d1b5b597c	Revert "gtid: Refactor reconnect logic & prevent events_count reset" ... This reverts commit 0a70fd515f.	7 months ago
Wazir Ahmed	0a70fd515f	gtid: Refactor reconnect logic & prevent `events_count` reset ... Signed-off-by: Wazir Ahmed <wazir@proxysql.com>	8 months ago
René Cannaò	c2f1871adf	Make set_thread_name() optional	1 year ago
Andriy Utkin	5e79afa8e0	Set thread names	2 years ago
Javier Jaramago Fernández	3e8d672c33	Remove commented code from original GTID impl	2 years ago
Javier Jaramago Fernández	317ef31e5a	Fix memory leak on GTID 'new_connector'	2 years ago
René Cannaò	e7aa5ff4c5	Split of MySQL_HostGroups_Manager.cpp into multiple files ... First commit to split MySQL_HostGroups_Manager.cpp into multiple files. More to split.	2 years ago