proxysql

Commit Graph

Author	SHA1	Message	Date
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
Javier Jaramago Fernández	25c6cf9dff	Fix 'nlohmann::json' type forwarding	2 years ago
Javier Jaramago Fernández	bbda0a86eb	Add initial impl for dual-password support	2 years ago
René Cannaò	fde8ace076	Removed json.hpp from include files This seems to speedup compile time, and also lead to smaller binary	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ò	73f8ad0a35	Code split related to generate_proxysql_internal_session_json	2 years ago
René Cannaò	d92c2d2e29	Implementation of MySQL_Connection::set_ssl_params	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ò	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
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	b588798a08	Few fixes	3 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.	3 years ago
Javier Jaramago Fernández	0d8860e8a2	Remove old commented code for 'IsActiveTransaction' impl	3 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ò	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
Rahim Kanji	dbfb99ce71	* Added hostname and ip information in mysql_connection * Added multiple IP support with load balancing (Round Robin Scheduling) * Added DNS resolver request max queue size * Added AI_ADDRCONFIG flag * Exception handling	3 years ago
Javier Jaramago Fernández	bcc6532d66	Modify previous impl for 'auto_increment_delay_multiplex_timeout_ms' and fix 'connection_delay_multiplex_ms' This commit contains an implementation rework and a fix: - Impl for 'auto_increment_delay_multiplex_timeout_ms' has been reworked in favor of reusing 'wait_until' to share logic with previous 'connection_delay_multiplex_ms' variable. - Fix previous 'connection_delay_multiplex_ms' behavior preventing connection retaining when traffic unrelated to target hostgroup is being received by the session.	4 years ago
Javier Jaramago Fernández	a67db17709	Fix current 'auto_increment_delay_multiplex_timeout_ms' behavior #3923	4 years ago
René Cannaò	f7d8824379	Trying to work around MySQL bug 107875 Because of MySQL bug https://bugs.mysql.com/bug.php?id=107875 , autocommit=0 can "create a transaction" even if SERVER_STATUS_IN_TRANS is not set. This means that a SAVEPOINT can be created in a "transaction" created with autocommit=0 but without SERVER_STATUS_IN_TRANS . This commit takes also care of scenarios when autocommit=0 was switched back to autocommit=1 when a SELECT was executed while variable mysql-enforce_autocommit_on_reads was false. MySQL_Session::NumActiveTransactions() now accepts a flag to check for savepoints.	4 years ago
René Cannaò	ea721ff31b	Merge pull request #3754 from sysown/v2.x-group_replication_consistency Add support for more session variables #3731 #3761 #2702	4 years ago
René Cannaò	50f1c9f61a	Removed reference to STATUS_MYSQL_CONNECTION_NO_BACKSLASH_ESCAPES STATUS_MYSQL_CONNECTION_NO_BACKSLASH_ESCAPES was an internal status in ProxySQL , now deprecated	4 years ago
René Cannaò	25fc1def8e	Fixed a buffer overflow in new variables	4 years ago
René Cannaò	241a5e54d7	Draft to reimplement how session variables are handled	5 years ago
René Cannaò	bc4109404b	Remove unused variables	5 years ago
René Cannaò	2ce9ed9686	Disabled in MySQL_Connection code related to store results	5 years ago
Javier Jaramago Fernández	4b81e21d57	Added comments, simplified 'stmt->result.data' assignment and minor cleanup for 'process_rows_in_ASYNC_STMT_EXECUTE_STORE_RESULT_CONT'	5 years ago
René Cannaò	7921e130d2	Third commit to buffer resultsets in Prepared Statements * MySQL_ResultSet() stores a pointer to the PS * MySQL_ResultSet::init_with_stmt() doesn't need anymore the pointer to the PS Furthermore, it isn't anymore an "init" but an end (we will rename it) * Added MySQL_ResultSet::add_row(MYSQL_ROWS rows) for PS only MySQL_Protocol::generate_pkt_row3() accepts an optional row length. If passed, it will know the length of the row without computing it * MyRS initialized during ASYNC_STMT_EXECUTE_STORE_RESULT_START * Implemented throttling during ASYNC_STMT_EXECUTE_STORE_RESULT_START * MySQL_Connection::process_rows_in_ASYNC_STMT_EXECUTE_STORE_RESULT_CONT() always generates a heartbeat. For now unnecessary, and we will better tune it later * test_ps_async-t.cpp tunes mysql-threshold_resultset_size to trigger buffering More testing is required	5 years ago
René Cannaò	5c0a732d8a	Second commit to buffer resultsets in Prepared Statements So far this seems to work, although it is dropping most of the rows. The rows are lost intentionally up to this commit.	5 years ago
René Cannaò	ba7b3aa1ed	Revert "Adding two new states in MySQL_Connection" This reverts commit `07e2b94125`.	5 years ago
René Cannaò	07e2b94125	Adding two new states in MySQL_Connection	5 years ago
René Cannaò	aaddb4e568	Port of #3001 to 2.1.0 , related to #3000 A client connection can use a backend connection with a session variable set by a different client	6 years ago
René Cannaò	5ce13abc36	Merge pull request #2881 from sysown/v2.1.0-2717 Refactored MySQL_Connection setter/getter functions functions for 'status_flags' #2717	6 years ago
René Cannaò	3d74ef4828	Merge pull request #2882 from sysown/v2.1.0-2862 Port PR 2829 to 2.1.0 #2862	6 years ago
Javier Jaramago Fernández	d10f519e4a	Refactored 'MySQL_Session' set/get status functions - Added extra doc about the 'status_flags' and 'server_status'. - Added 'sql_log_bin0' and 'prepared_statement' to the 'conn.status' from PROXYSQL SESSION INFO.	6 years ago
René Cannaò	00ce76e57e	Add support for SAVEPOINT #948	6 years ago
Javier Jaramago Fernández	8fafa66336	Removed unused variables from 'MySQL_Connection()'	6 years ago
val	d0d7018e34	rollback session_track_gtids	6 years ago
val	ade8491f47	Re-evaluate on_connect_to_backend	6 years ago
val	3e790c9083	Polishing and cleanup - cleanup code - performance optimization - use default value for connection	6 years ago
Valentin Rakush	61c1913334	Character set handling implementation	6 years ago
René Cannaò	c28deb7c7d	Generalize the use of session variables Added new array mysql_tracked_variables[] that defines the tracked variables. Ideally, tracking a new session variable will requires adding only a couple of lines of code. Removed session variables from mysql_thread_variables_names: - now both MySQL_Threads_Handler::get_variables_list() and MySQL_Threads_Handler::has_variable() rely on mysql_tracked_variables[] Simplified MySQL_Variables, as it now also uses mysql_tracked_variables[] . Simplify parser in MySQL_Session Generalized code to handle two variables together: - sql_auto_is_null - sql_safe_updates Migrating more session variables to new algorithm - collation_connection - net_write_timeout - max_join_size Migrating more session variables to new algorithm - collation_connection - net_write_timeout - max_join_size	6 years ago
Valentin Rakush	0e79eb39f7	Implementation of the session variables array - SQL_SAFE_UPDATES - SQL_SELECT_LIMIT - SQL_SQL_MODE - SQL_TIME_ZONE - CHARACTER_SET_RESULTS - SQL_TRANSACTION_ISOLATION - SQL_TRANSACTION_READ - SQL_SESSION_TRACK_GTIDS - SQL_SQL_AUTO_IS_NULL	6 years ago
val	cdbf70817a	Revert "Implementation of the session variables array" This reverts commit `1fb5c9cf06`.	6 years ago
val	b1339faefd	Revert "Generalize the use of session variables" This reverts commit `d242771a25`.	6 years ago
val	eb08620181	Revert "Character set handling implementation" This reverts commit `796ea5b215`.	6 years ago
val	8696ece34b	Revert "Polishing and cleanup" This reverts commit `dbafde2ff4`.	6 years ago
val	dbafde2ff4	Polishing and cleanup - cleanup code - performance optimization - use default value for connection	6 years ago
Valentin Rakush	796ea5b215	Character set handling implementation	6 years ago
René Cannaò	d242771a25	Generalize the use of session variables Added new array mysql_tracked_variables[] that defines the tracked variables. Ideally, tracking a new session variable will requires adding only a couple of lines of code. Removed session variables from mysql_thread_variables_names: - now both MySQL_Threads_Handler::get_variables_list() and MySQL_Threads_Handler::has_variable() rely on mysql_tracked_variables[] Simplified MySQL_Variables, as it now also uses mysql_tracked_variables[] . Simplify parser in MySQL_Session Generalized code to handle two variables together: - sql_auto_is_null - sql_safe_updates Migrating more session variables to new algorithm - collation_connection - net_write_timeout - max_join_size Migrating more session variables to new algorithm - collation_connection - net_write_timeout - max_join_size	6 years ago

1 2 3 4

152 Commits (48ba491cb7464656cf2cc86b82c19a97c042f923)