88 Commits (ffe56903605c3eeb6d09724e95bee29c8dad2a23)

Author	SHA1	Message	Date
Rene Cannao	b5598d8d53	Add comprehensive ProxySQL_Poll usage documentation throughout codebase ... Enhance ProxySQL_Poll class documentation with detailed usage patterns: - lib/ProxySQL_Poll.cpp: Enhanced file-level documentation with architecture overview, template specialization, memory management, and event processing pipeline explanations - lib/MySQL_Thread.cpp: Added usage documentation for listener registration, removal patterns, client session setup, and main poll loop - lib/PgSQL_Thread.cpp: Added equivalent PostgreSQL usage documentation mirroring MySQL patterns with protocol-specific details - lib/mysql_data_stream.cpp: Documented cleanup, receive activity tracking, and send activity tracking patterns - lib/PgSQL_Data_Stream.cpp: Documented equivalent PostgreSQL data stream patterns for cleanup and activity tracking All documentation is placed directly where code is used, avoiding specific line numbers for better maintainability. Includes comprehensive explanations of when, why, and how ProxySQL_Poll methods are used throughout ProxySQL's event-driven architecture. [skip-ci]	3 months ago
Javier Jaramago Fernández	5c8a32a0b0	Merge branch 'v3.0' of github.com:sysown/proxysql into v3.0-handle_unexp_ping	4 months ago
Javier Jaramago Fernández	6fea828e86	Improve logging in unexpected COM_PING packet handling ... Logging messages now include 'client address', 'session status' and 'data stream status'. Client address is also logged when OK packets are dispatched, this should help tracking if a client has received the expected packets or not.	4 months ago
René Cannaò	2667540fcc	Merge pull request #5237 from sysown/v3.0_pgsql-monitor-sslsupport-5205 ... Add SSL support for backend connections in PGSQL monitor	4 months ago
Rahim Kanji	fae283cf7e	Add SSL and non-SSL connection OK metrics for PostgreSQL monitor connections ... Adds two new metrics, ssl_connections_OK and non_ssl_connections_OK, to improve visibility into PostgreSQL monitor connection status.	4 months ago
René Cannaò	3c4e09fec0	Merge pull request #5225 from sysown/v3.0_refactor_prepared_statement_cache_design_5211 ... Refactored Prepared-Statement Cache Design (Lock-Free Hot Path) - Part 2	4 months ago
Rahim Kanji	9c0e14a5d1	Replace rand() with lock-free Xoshiro128++ PRNG	4 months ago
Rahim Kanji	1a48aadf5e	Code cleanup	4 months ago
René Cannaò	8be91071ef	Merge pull request #5190 from sysown/v3.0_default_interface_global_var_5189 ... Ensure default mysql-interfaces=0.0.0.0:6033 and pgsql-interfaces=0.0.0.0:6133 are set	5 months ago
Rahim Kanji	48928ce04e	Ensure default mysql-interfaces=0.0.0.0:6033 and pgsql-interfaces=0.0.0.0:6133 are set	5 months ago
Rahim Kanji	86c17f04d7	Replace single sleep with looped delay for simulated watchdog test	5 months ago
Wazir Ahmed	5219d4be93	processlist: Prevent crash due to SQLITE_TOOBIG ... - Add new mysql/pgsql variable `processlist_max_query_length`. - Min: 1K - Max: 32M - Default: 2M - Truncate current query based on the configuration before inserting into `stats_*_processlist` tables. - Refactor/fix code related to other processlist configurations. 1. `session_idle_show_processlist` value was not updated in `ProxySQL_Admin.variables`. 2. Pass processlist config as an argument to `MySQL_Threads_Handler::SQL3_Processlist` instead of using thread-local variables. Signed-off-by: Wazir Ahmed <wazir@proxysql.com>	6 months ago
René Cannaò	abafaccbc0	Merge pull request #5156 from sysown/v3.0_pgsql_stat_activity_issue_4682 ... Add backend_pid and backend_state to stats_pgsql_processlist and create stats_pgsql_stat_activity view	6 months ago
Rahim Kanji	f3ea179384	Add backend PID/state to stats_pgsql_processlist and create pg_stat_activity-style view ... - Added `backend_pid` and `backend_state` columns to `stats_pgsql_processlist` to display PostgreSQL backend process ID and connection state. - Created `stats_pgsql_stat_activity` view on top of `stats_pgsql_processlist` with column aliases matching PostgreSQL's `pg_stat_activity` for consistency.	6 months ago
Rahim Kanji	4d91452fc5	Implement backend query cancellation for PostgreSQL #5136 ... Add support for PostgreSQL query cancellation and backend termination features to allow clients to cancel long-running queries and terminate connections through the standard PostgreSQL protocol. Features implemented: - Intercept pg_backend_pid() queries and return ProxySQL session thread ID - Intercept pg_terminate_backend() to terminate client connections asynchronously - Intercept pg_cancel_backend() to cancel queries on backend connections - Support Cancel Request protocol via separate connection with PID and secret key validation - Return BackendKeyData message on successful authentication with session thread ID and unique cancel secret key This enables clients to use standard PostgreSQL cancellation mechanisms (pg_cancel_backend, pg_terminate_backend, and Cancel Request protocol) while ProxySQL maintains proper session isolation and maps client requests to appropriate backend connections.	6 months ago
Rahim Kanji	a89291c9a9	Added query logging support for PostgreSQL	7 months ago
Rahim Kanji	8d8577b0ad	Ensure PgSQL_Threads_Handler and PgSQL_HostGroups_Manager objects are released when ProxySQL shuts down or restarts.	8 months ago
Rahim Kanji	ce94a7080a	Merge branch v3.0_session_param_reset_connection into v3.0_extended_query_protocol	8 months ago
Rahim Kanji	50243ef283	Corrected RESET/DEFAULT logic ... * Now will actually reset value to server default (represented by nullptr value), if that parameter is not set in startup parameter. * Default parameter values (pgsql_default_*) will now be set only for critical parameters.	8 months ago
Rahim Kanji	344ba25777	Add Watchdog PROXYSQLTEST covering MySQL and PgSQL threads	9 months ago
Rahim Kanji	3619fa5d21	Added pgsql-max_stmts_per_connection variable	9 months ago
Rahim Kanji	bc87d0d901	* For a Describe Portal message, peek at the next message in the extended query frame. If it is an Execute message, indicating that client is sending a Bind/Describe/Execute sequence ... skip processing the Describe Portal. This is because libpq automatically includes a Describe Portal during execution, and sending it again would be redundant. * Removed server_capabilities from PgSQL modules	9 months ago
Rahim Kanji	87ad15b01c	* Removed autocommit_on_hostgroup from PostgreSQL modules ... * Introduced an error generator method to reduce code duplication * Added several comments for clarity * Addressed edge cases related to libpq limitations	9 months ago
Rahim Kanji	48ba491cb7	Add support for unnamed Describe Portal and improve extended query handling ... - Always send Describe Portal to the backend - Enforce check for unnamed portals in Bind, Describe, Close, and Execute; raise errors for named portals - Improve error handling for extended query flow - Introduce Extended_Query_Info struct to unify extended query-related members and reduce redundancy	9 months ago
Rahim Kanji	f350102f72	Code cleanup	9 months ago
Rahim Kanji	a741598a8d	Added Describe message handling	10 months ago
Rahim Kanji	24fecc1f6e	Add PostgreSQL extended query (prepared statement) support in ProxySQL ... This commit lays the groundwork for handling PostgreSQL’s extended query protocol (prepared statements) by introducing parsing, it's caching and execution framework stubs. - Implement Parse handling - Implement caching of parse (reuse) - Introduce Execute framework stub for future binding and execution logic.	10 months ago
Rahim Kanji	f9232ae50d	Merge remote-tracking branch 'Master/v3.0' into v3.0_session_parameter_tracking	1 year ago
Rahim Kanji	6603d48bb0	Optimized and simplified PostgreSQL variable Validator	1 year ago
Rahim Kanji	a5b7063cf3	Add validation for PostgreSQL patameters/variables and default PostgreSQL variables ... * Added validation checks when setting PostgreSQL variables to prevent invalid configurations. * Applied the same validation to default PostgreSQL variables to maintain consistency.	1 year ago
Rahim Kanji	e6ddae643b	Now, default variables are set for all tracked variables ... Improved error handling	1 year ago
Rahim Kanji	d2c333dcfd	Special handling of PostgreSQL DateStyle in ProxySQL ... - DateStyle consists of two values: a format and an order (e.g., ISO, MDY). Unlike other parameters, DateStyle can be set with one or both values, and the missing value retains its previous setting. Examples: SET DateStyle TO 'ISO, MDY' → Format: ISO, Order: MDY SET DateStyle TO 'ISO' → Format: ISO, Order remains unchanged i.e MDY SET DateStyle TO 'DMY' → Format remains unchanged i,e ISO, Order: DMY SET DateStyle TO 'Postgres' → Format: Postgres, Order remains unchanged i.e DMY Improved RESET statements and DEFAULT parameter values handling - Enhance RESET and DEFAULT value handling: • When a parameter is RESET or set to DEFAULT, ProxySQL now first checks if a value is provided in the connection options. • If a connection value is specified, it is applied; otherwise, the parameter falls back to the value defined by the corresponding pgsql-default_* variable.	1 year ago
Rahim Kanji	35b2dd593d	Separate implementation of SET statement parser for MySQL and PostgreSQL	1 year ago
René Cannaò	c2f1871adf	Make set_thread_name() optional	1 year ago
Rahim Kanji	0e1392322f	RESET oaramter and DEFAULT parameter value handling (not fully tested yet) ... * New tracked variables added: - bytea_output - client_min_messages - escape_string_warning Few optimizations Code cleanup	1 year ago
Rahim Kanji	06e496b7c3	Added tracking of parameters: ... * client_encoding/names * datestyle * timezone/time zone * standard_conforming_strings	1 year ago
Rahim Kanji	b4e9060f71	Modified Set Parser	1 year ago
Rahim Kanji	794ec0f48d	Merge remote-tracking branch 'Master/v3.0' into v3.0_dynamic_fast_forward	1 year ago
Rahim Kanji	2aa60e3231	Added Session Type in logs	1 year ago
Rahim Kanji	395a977e68	Merge branch 'v3.0'	1 year ago
Rahim Kanji	f33fd02c37	Add COPY ... FROM STDIN detection regex	1 year ago
Rahim Kanji	967386d7d3	Added the SESSION_FORWARD_TYPE enum to define the type of session forwarding	1 year ago
Javier Jaramago Fernández	74c74adf5e	Prevent busy-waiting in active wait during 'listener_del' ... Since the operation of stopping each worker thread listeners is performed during 'maintenance_loops', the active wait taking place in 'listener_del' is likely to take some time. A sensible delay has been added to reduce unneccesary load.	1 year ago
Javier Jaramago Fernández	8bc60ed283	Fix worker threads stalling race condition on RESUME command ... During a RESUME operation, if a 'MySQL_Thread' is bootstrapping listeners (in `MySQL_Thread::run_BootstrapListener`) and detect that `MySQL_Threads_Handler::bootstrapping_listeners` is 'false', the thread prematurely shuts down its own bootstrapping flag from 'mypolls' (`ProxySQL_Poll::bootstrapping_listeners`). Since this thread wont ever bootstrap its corresponding listening sockets, the other working threads will be stalled waiting on it, eventually triggering the watchdog and crashing the instance. Since the bootstrapping operation is sequential, it's expected that all the threads but the one starting their listening sockets are in an active wait. A sensible delay has been introduced to reduce the overhead of such wait.	1 year ago
Rahim Kanji	6d614a4b99	Merge branch 'v3.0'	1 year ago
Javier Jaramago Fernández	100630fba5	Second iteration on PostgreSQL monitoring POC ... This commit packs multiple fixes/improvements: - Added READONLY support for PostgreSQL. - Major rework for queries and statements used on monitoring checks: + Checks/Actions rewrote for single instance checks. + Reuse of prepared statements instance of re-preparation. - Fixed missing error handling in connection creation state machine. - Fixed connection rotation in connection pool (now FIFO). - Added support for configurable batching in scheduler thread, via '*_interval_window' variables. These variables allows to define the burstiness of the scheduling within the processing interval. - Added new config variable 'pgsql-monitor_dbname'. Allows to control which 'db' will be target by monitoring connections. - Several fixes for 'poll' timeout computation for worker threads. - Fixed edge cases for current interval detection. - Reduced deviation in scheduling intervals computation. - Refactored and simplified connection event handling. - Improved error messages for monitoring actions. - Replaced several invalid uses of 'mysql_thread___monitor_*' in favor or new 'mysql_thread___monitor_*' variables. - Honor '-M' argument for disabling monitoring support.	1 year ago
Rahim Kanji	1c70a9c35c	Enabled pgsql-query_cache_stores_empty_result	1 year ago
Rahim Kanji	a49a33c354	Released memory allocated for pgsql_thread___monitor_username and pgsql_thread___monitor_password during the destruction of the PgSQL_Thread	2 years ago
Rahim Kanji	720441af20	Refactored and Optimized Query Cache with PgSQL Support ... * Added Query Cache Support for PgSQL: * Introduced new variables for PgSQL Query Cache management: * pgsql-query_cache_size_MB * pgsql-query_cache_soft_ttl_pct * pgsql-query_cache_stores_empty_result * pgsql-query_cache_handle_warnings (not yet utilized) * Overwriting Transaction Status: * Sending current transaction state to the client when a result is returned from the query cache. * This currently does not differentiate between normal and error transaction states—both are treated as active transaction states. * Cache Lifetime Management: Replaced manual reference counting with std::shared_ptr to efficiently manage the lifecycle of cache entries, ensuring proper memory deallocation and reducing complexity. * Unified Purging Logic: Refactored the query cache purging logic to use a single thread for both MySQL and PgSQL cache entries. * Code Cleanup: Removed unnecessary methods and data members to streamline the codebase and improve maintainability. * Performance Optimization: Improved memory management, reducing memory footprint and enhancing performance.	2 years ago
Javier Jaramago Fernández	705f50e0f9	Add initial POC for PostgreSQL monitoring support	2 years ago