423 Commits (cf8cbfd89af57656a4a3253c7d0832ce25728fad)

Author	SHA1	Message	Date
Rene Cannao	5485bb02f4	Improve fast forward replication CLIENT_DEPRECATE_EOF validation ... Enhance the match_ff_req_options function to better handle CLIENT_DEPRECATE_EOF flag validation in fast forward replication scenarios. The function now performs a more robust check by examining the actual MySQL command type when the initial CLIENT_DEPRECATE_EOF flags don't match between frontend and backend connections. Key improvements: - Special handling for binlog-related commands (_MYSQL_COM_BINLOG_DUMP, _MYSQL_COM_BINLOG_DUMP_GTID, _MYSQL_COM_REGISTER_SLAVE) that should be allowed even when CLIENT_DEPRECATE_EOF flags don't match - Proper packet parsing to extract and validate MySQL command types - Enhanced compatibility for fast forward replication connections with mixed deprecate EOF configurations This change ensures that ProxySQL can handle more complex replication scenarios while maintaining proper protocol validation.	3 months ago
René Cannaò	d3f06c537f	Merge branch 'v3.0' into v3.0-ff_conns_eof_caps_match	11 months ago
René Cannaò	e0e4d0652b	Fix issue #4841 ... Incorrectly attempt to use a collation with id larger than 255 during backend handshake Problem: When creating a backend connection, if the frontend connection has configured a collation with id larger than 255 (for example using SET NAMES utf8mb4 COLLATE utf8mb4_0900_as_ci; , ProxySQL may try to create a new connection using such collation. The problem is that at protocol level, during handshake only 1 byte can be used to configure the collation. That means that if ProxySQL sets a collation greater than 255 , only the less significant byte is used. Therefore even if ProxySQL believes that the backend connection will use the specified collation, mysql_real_connect() is using a different collation. For example, using collation 305 will lead to use collation 49 (305-256). Solution: When a collation id greater than 255 is detected, the default collation for that character set is used. ProxySQL will later issue a SET NAMES ... COLLATE to address the mismatch.	1 year ago
Javier Jaramago Fernández	d49a96dade	Enforce 'CLIENT_DEPRECATE_EOF' capability match for fast-forward ... - Ensures matching for 'CLIENT_DEPRECATE_EOF' capability when creating or acquiring backend conns for 'fast-forward' sessions. - Since 'CLIENT_DEPRECATE_EOF' capability isn't enforced on backend connections for regular sessions, a mismatch between client and backend capabilities is possible. A verification has been introduced when a session switches to 'fast-forward', in case of capabilities mismatch, an error is logged and client disconnected.	1 year ago
René Cannaò	7ef5993c35	Revert "Enforce 'CLIENT_DEPRECATE_EOF' capability match for conn-pool" ... This reverts commit 50ce205d21.	1 year ago
Javier Jaramago Fernández	50ce205d21	Enforce 'CLIENT_DEPRECATE_EOF' capability match for conn-pool ... Add new config option ('mysql-connpool_match_client_deprecate_eof') that allows to control whether to enforce a match between fronted and backend connections for 'CLIENT_DEPRECATE_EOF' capability. By default, this option is 'true', allowing smooth transitions from regular sessions to 'fast_forward'.	1 year ago
Rahim Kanji	395a977e68	Merge branch 'v3.0'	1 year ago
Rahim Kanji	967386d7d3	Added the SESSION_FORWARD_TYPE enum to define the type of session forwarding	1 year ago
Rahim Kanji	6d614a4b99	Merge branch 'v3.0'	1 year ago
Rahim Kanji	3b5671267f	Implemented overflow-safe multiplication for mysql_thread___threshold_resultset_size and pgsql_thread___threshold_resultset_size	1 year ago
Rahim Kanji	cb35d65d73	If query results needs to be cached, the mysql_thread___query_cache_size_MB setting takes precedence over mysql_thread___threshold_resultset_size	1 year ago
René Cannaò	04abd43a57	Initial commit with PostgreSQL support	1 year ago
Rahim Kanji	c5bc9ed2c6	DNS Cache Fixes ... * If a MySQL connection fails or times out for a specific hostname, the corresponding DNS record will be removed from DNS Cache. This ensures that outdated DNS records are not retained. (Rest of the DNS resolution process remains unchanged) * DNS cache functionality will automatically be disabled when ProxySQL is run with the -M or --no-monitor option.	1 year ago
Javier Jaramago Fernández	05f7c42f9e	Improve context on 'MYSQL_OPT_NONBLOCK' for SSL connections	2 years ago
Rahim Kanji	ca93da5857	Resolved conflicts	2 years ago
René Cannaò	fcc800e390	Documentation on MySQL_Connection::async_query()	2 years ago
René Cannaò	2d89f06a5a	Refactoring of ProcessQueryAndSetStatusFlags()	2 years ago
René Cannaò	4264e9349d	Refactoring MySQL_Connection::connect_start()	2 years ago
René Cannaò	43b077efca	set fileencoding on mysql_connection.cpp ... :set fileencoding=utf-8 on mysql_connection.cpp	2 years ago
Rahim Kanji	c7cf5ba344	Removed MySrvStatus class	2 years ago
René Cannaò	73f8ad0a35	Code split related to generate_proxysql_internal_session_json	2 years ago
Rahim Kanji	a081695ae9	* Solved few warnings ... * Enforced explicit conversion of MySrvStatus	2 years ago
Rahim Kanji	8c92f9292a	A hostgroup can now be configured to have a maximum number of online servers simultaneously. Once this limit is reached, any new connections attempting to access the connection pool will be denied, and existing connections will gradually be reassigned to the available connection pool until the number of online servers is reduced to meet or fall below the specified maximum.	2 years ago
René Cannaò	1bc9d9e5f4	Several code documentation	2 years ago
René Cannaò	d92c2d2e29	Implementation of MySQL_Connection::set_ssl_params	2 years ago
René Cannaò	8ab51c65e7	ssl_params: use NULL instead of empty string #4466 ... If values in mysql_servers_ssl_params are empty strings, they needs to be passed as NULL arguments in mysql_ssl_set() and mysql_options() Closes #4466	2 years ago
René Cannaò	548ededd4f	Include MySQLServers_SslParams in MySQL_Connection ... This allows to preserve the parameters, and output in the error log if needed	2 years ago
René Cannaò	9a7c3e8196	Introducing mysql_servers_ssl_params ... First commit to introduce table mysql_servers_ssl_params . This allows to configure per host SSL parameters.	2 years ago
René Cannaò	41cd740701	Added metric MultiplexDisabled_ext #4241 ... In the output of PROXYSQL INTERNAL SESSION and stats_mysql_processlist.extended_info , MultiplexDisabled was only returning the output of MySQL_Connection::MultiplexDisabled() . If there was a transaction, or an error, multiplexing was disabled but MultiplexDisabled() was still reporting false. Therefore it was necessary to also check server_status flag and last_errno. This commits intruduces MultiplexDisabled_ext , that reports the output of: MySQL_Connection::MultiplexDisabled() || MySQL_Connection::isActiveTransaction() This should make troubleshooting easier. Also, removed any reference to deprecated STATUS_MYSQL_CONNECTION_TRANSACTION . Closes #4241	2 years ago
René Cannaò	699fe7efcd	Moved proxysql_find_charset_* functions out of MySQL_Thread.cpp	2 years ago
Rahim Kanji	e1c489acb1	* If the backend server has CLIENT_DEPRECATE_EOF enabled, and the client does not support CLIENT_DEPRECATE_EOF, warning_count will be '0' in intermediate EOF packet. ... * Suppress the display of warning counts in the "SHOW WARNINGS" statement.	2 years ago
Rahim Kanji	045d6bcaeb	* Execute all test cases with 'CLIENT_DEPRECATE_EOF' both enabled and disabled. ... * Introduced 'ps_type' enum to differentiate between preparing a statement and executing a statement * Fixed issue where the warning count fails to reset when the SET statement generates a warning. * Resolved the issue where the 'server_status' and 'warning count' were not accurately represented in the statement. * Replaced 'mysql_warning_count' with 'mysql_stmt_warning_count' for retrieving the warning count in statements. * Added 'handle_warning' field in hostgroup_attributes TAP test * Updated warnings TAP test	2 years ago
Rahim Kanji	dae3d669b9	* Setting 'warning_count' as soon as query is executed. ... * 'MySQL_Connection::warning_count' will be globally employed for managing multiplexing control and transmitting the warning count to the client * Fixed prepare statement bug: When preparing, if the digest matches, the result set is retrieved from the cache and sent to the client. Note: Currently using 'mysql_warning_count' to retrieve the warning count for prepared statement.	2 years ago
Rahim Kanji	05208e2839	* Update warning_count as soon as query is executed.	2 years ago
Rahim Kanji	743cd502a5	* Updated variable name from 'mysql-query_cache_with_warnings_support' to 'mysql-query_cache_handle_warnings' ... * Introduced global variable 'mysql-handle_warnings' to control warning support in ProxySQL * Included 'handling_warnings' flag in the 'mysql_hostgroup_attributes' table (hostgroup_settings). This flag holds top priority and can override the value of the global variable 'mysql_handle_warnings'.	2 years ago
Rahim Kanji	b588798a08	Few fixes	2 years ago
Rahim Kanji	6b295477d6	Enhanced Warnings handling in ProxySQL: ... * Implemented 'SHOW WARNINGS' and 'SHOW COUNT(*) FROM WARNINGS' query handling. * When a query produces warnings, the warning count is now included in the query response. Additionally, a new variable 'mysql-query_cache_with_warnings_support' has been introduced for the query cache feature: * A value of '0' means that if a query execution produces warnings, the resultset will not be saved in the query cache. * A value of '1' indicates that if a query produces warnings, the resultset will be saved in the query cache, but the warning count in that resultset will be set to '0'. ** Note: * Warning handling is dependent on the query digest and 'mysql-query_digests' must be enabled for it to work. * Warnings saved in logfile ['mysql-log_mysql_warnings_enabled'] and the current feature can work in conjunction with each other.	2 years ago
Javier Jaramago Fernández	bb40e9e431	Fix 'COMMIT|ROLLBACK' forwarding to backend connections - Closes #4264 ... These commands are now forwarded to the backend connections from a session with potential transaction statuses, using the following priority order: 1. Connections flagged with 'SERVER_STATUS_IN_TRANS', or 'autocommit=0' when 'autocommit_false_is_transaction' is set. 2. Connections with 'autocommit=0' holding a 'SAVEPOINT'. 3. Connections with 'unknown transaction status', e.g: connections with errors.	3 years ago
René Cannaò	db632cd7f5	Preserve STATUS_MYSQL_CONNECTION_COMPRESSION after connection reset ... In MySQL_Connection::reset() we were forgetting the value of STATUS_MYSQL_CONNECTION_COMPRESSION. De-facto disabling compression if it was enabled.	3 years ago
Rahim Kanji	ff722142bf	SSL support on Unix Socket reinstated	3 years ago
Rahim Kanji	a1fcf5d94f	Added SSLKeylog in ProxySQL Modules	3 years ago
Rahim Kanji	8f899e34f9	Added support for SSLKEYLOGFILE ... * 'admin-ssl_keylog_file' variable has been introduced to allow users to specify the path for the SSLKEYLOG file. The file path can be an absolute path or relative to the ProxySQL data directory. * Assigning an empty path to the 'admin-ssl_keylog_file' variable signifies that the SSLKEYLOG file feature is disabled. * In case an invalid path is provided for the SSLKEYLOG file, ProxySQL will automatically revert to the last valid path value. * 'PROXYSQL FLUSH LOGS' command can be used to rotate SSLKEYLOG file. # Conflicts: # lib/mysql_connection.cpp	3 years ago
Rahim Kanji	cd352ff141	Disable SSL and Compression for UNIX Socket	3 years ago
Rahim Kanji	3865c81873	DNS Cache module has been updated so that it no longer regards the UNIX socket path as a hostname.	3 years ago
René Cannaò	069140f79e	Automatically start a transaction when running a query ... This commit also introduces 2 output for PROXYSQL INTERNAL SESSION: - active_transactions - transaction_started_at Enhanced the TAP tests to also verify the above metrics	3 years ago
René Cannaò	e487ddf8ec	Set correct backend encryption when switching to fast_forward ... When receiving MYSQL_COM_BINLOG_DUMP , MYSQL_COM_BINLOG_DUMP_GTID or MYSQL_COM_REGISTER_SLAVE , proxysql automatically switches to fast_forward . Although it is important to correctly configure "encrypted" in the backend data stream if needed. Used PMC-10005 for reference , as this is implemented similarly in many parts of the code. During the switch proxy_info() now also reports the client and the command received.	3 years ago
René Cannaò	f3c604eb84	Implemented mysql_hostgroup_attributes.multiplex ... If mysql_hostgroup_attributes.multiplex: - 0 : multiplexing is always disabled - 1 : multiplexing is enabled for the hostgroup, but other criteria can disable multiplexing (transaction, temp tables, query rules, etc)	3 years ago
René Cannaò	71e2510ef6	Code cleanup on MySQL_HostGroups_Manager ... Some rework to try to reduce duplicated code	3 years ago
René Cannaò	a2be18881a	Merge pull request #4062 from sysown/v2.x-fast_forward_ssl2 ... Support for fast_forward and SSL #1459	3 years ago
Rahim Kanji	4e44551dd2	ProxySQL crashes if client is not able to keep up with records returned and query has a warning condition ... Show Warning check is added to avoid infinite loop	3 years ago