proxysql

Commit Graph

Author	SHA1	Message	Date
Rahim Kanji	2046d92b70	Merge remote-tracking branch 'v3.0' into v3.0_pgsql_meta_command_describe_table	4 weeks ago
Rahim Kanji	ca45405942	Merge remote-tracking branch 'Master/v3.0-moveInfra' into v3.0_pgsql-pipeline-set-reset-discard-fix-5432	1 month ago
Rene Cannao	6b46b26931	chore: implement PR review feedback for release tier system - Makefile: normalized GIT_VERSION by stripping 'v' prefix before arithmetic. - Makefile: corrected .PHONY declaration for build_deps_debug_default. - Admin Handler: properly guarded TSDB commands to return error when disabled. - REST API: removed redundant nested guards inside tsdb_resource class. - Statistics: implemented rigorous input validation for set_variable. - Statistics: added return value checks and rollback logic for TSDB migrations. - Statistics: implemented bounded concurrency (batching) for backend probes. - FFTO: implemented cumulative buffer limit enforcement in MySQL and PgSQL. - FFTO: ensured initial packet capture in PgSQL_Session by early initialization. - FFTO: improved reassembly buffer compaction logic. - Headers: default-initialized ffto_bypassed to false. - Code cleanup: merged redundant PROXYSQLFFTO guards.	1 month ago
Rene Cannao	c2f678a9de	feat: implement release tiers and feature guards for v3.0, v3.1, and v4.0 This commit introduces a structured release tier system controlled by environment variables, allowing three distinct ProxySQL versions to be built from the same codebase while maintaining a clear upgrade path. Key Changes: - Tier 1 (v3.0.x Stable): Default build including bug fixes and core enhancements. - Tier 2 (v3.1.x Innovative): Enabled via PROXYSQL31=1. Adds FFTO and TSDB. - Tier 3 (v4.0.x AI/MCP): Enabled via PROXYSQLGENAI=1. Adds the AI stack. Implementation Details: - Makefile: Implemented dynamic versioning logic that increments the minor version for v3.1 and the major version for v4.0. Added tier documentation. - Feature Guards: Introduced PROXYSQLFFTO and PROXYSQLTSDB guards across ProxySQL_Admin, ProxySQL_Statistics, REST API, and HTTP server. - FFTO: Guarded Fast Forward Traffic Observer in MySQL and PgSQL sessions, including thread-local variables and configuration parameters. - TSDB: Guarded the entire Time Series Database subsystem, including SQLite table definitions, background loops, and REST API endpoints. - Build Fixes: * Fixed 'proxy_debug_func' linkage by adding extern "C" and moving the definition outside of DEBUG guards to ensure non-debug builds link correctly. * Corrected misplaced/nested DEBUG and PROXYSQLFFTO guards. * Verified build stability for all tiers (unset, PROXYSQL31=1, PROXYSQLGENAI=1).	1 month ago
Rahim Kanji	e84433159b	Merge remote-tracking branch 'v3.0' into v3.0_pgsql-pipeline-set-reset-discard-fix-5432	1 month ago
Rahim Kanji	742ff05ecc	Fix PostgreSQL transaction state management for pipeline mode Move transaction state tracking from RequestEnd to connection handler to enable proper binary pipeline mode support: - Call handle_transaction_state() at ASYNC_QUERY_END/ASYNC_STMT_EXECUTE_END in PgSQL_Connection instead of RequestEnd - Add reset_state() calls in 7 locations to prevent stale state: * Session reset * Connection detach (finishQuery) * Error handlers (4 paths) * Base session housekeeping - Refactor destructor to use reset_state() Fixes transaction state tracking in pipeline mode where connections can be returned to pool mid-transaction.	1 month ago
Rahim Kanji	176362c77d	Addressed feedback from AI review	1 month ago
Rahim Kanji	a82d653c0b	Handle late COPY protocol messages after session exits fast_forward mode When a COPY FROM STDIN operation encounters an error, the session switches back to normal mode. However, the client may have already pipelined CopyData('d'), CopyDone('c'), or CopyFail('f') messages that are still in the input queue. Previously, these messages fell through to the default case, generating a spurious "Feature not supported" error. This change adds explicit handling to discard these messages when session_fast_forward == SESSION_FORWARD_TYPE_NONE, preventing the race condition from causing errors. The client does not expect a response for these messages in this scenario.	1 month ago
Rene Cannao	3a3be5a559	Implement Fast Forward Traffic Observer (FFTO) for MySQL and PostgreSQL - Added TrafficObserver base interface - Implemented MySQLFFTO and PgSQLFFTO classes for protocol-aware observation - Integrated FFTO hooks into MySQL and PostgreSQL session handlers in FAST_FORWARD state - Added configuration variables: mysql-ffto_enabled, mysql-ffto_max_buffer_size, pgsql-ffto_enabled, pgsql-ffto_max_buffer_size - Implemented query digest extraction and reporting parity with internal stats - Added session-level bypass when packet size exceeds buffer threshold - Included architectural documentation in doc/ffto_design.md	2 months ago
Rahim Kanji	409070faa7	Add PostgreSQL \d tablename describe table support in Admin Handler Extend \d meta-command to support \d tablename for describing specific tables. Implements handlers for all 8 queries in the describe sequence: - Query 1: pg_class lookup with c.relname OPERATOR (extracts/caches table) - Query 2: pg_class attributes with c.oid= (table metadata) - Query 3: pg_attribute with PRAGMA table_info() (column information) - Queries 4-8: pg_policy, pg_statistic_ext, pg_publication, pg_inherits (return empty results as SQLite lacks these features)	2 months ago
Rahim Kanji	ce42c188f5	Improvements	3 months ago
Rahim Kanji	a1e10e3055	Add parameterized PID support for pg_cancel_backend/pg_terminate_backend This commit extends the existing pg_cancel_backend() and pg_terminate_backend() support to work with parameterized queries in the extended query protocol. While literal PID values were already supported in both simple and extended query protocols, this enhancement adds support for parameterized queries like SELECT pg_cancel_backend($1).	3 months ago
Rahim Kanji	556b1023c4	Removed change_user_auth_switch flag	3 months ago
Rahim Kanji	c0f99c0e15	Refactor: Improved Prepared-Statement Cache Design (Lock-Free Hot Path) #5211 Concurrency and Memory Management * Lock-Free Ref Counting: Replaced global mutex-protected integer reference counts with `std::atomic<uint32_t>` within `PgSQL_STMT_Global_info`, eliminating lock contention during statement referencing. * Modern Ownership: Adopted std::shared_ptr<const PgSQL_STMT_Global_info> for global and local storage, providing automatic, thread-safe memory and lifecycle management. * Memory Optimization: Removed redundant auxiliary maps `global_id_to_stmt_names` and `map_stmt_id_to_info` from local and global statement managers respectively, reducing overall memory overhead. * Optimized Purging: Statement removal logic was simplified for efficiently identifying and cleaning up unused statements. Hot Path Performance (`BIND`, `DESCRIBE`, `EXECUTE`) * Bypassed Global Lookups: Local session maps now store the `shared_ptr` directly, removing the need to acquire the global lock and search the global map during hot path operations. * Direct Refcount Manipulation: Refcount modification functions now operate directly on the passed statement object, eliminating the overhead of searching the global map to find the object pointer based on statement id. Safety and Protocol Logic (`PARSE`) * Efficient Statement Reuse: Implemented a local fast path check for the unnamed statement (`""`), allowing immediate reuse of an identical query (same hash) upon re-parse, which bypasses global processing and locks. Cleanup * Cleaned up and class rename `PgSQL_STMT_Manager_v14` -> `PgSQL_STMT_Manager`.	4 months ago
Rahim Kanji	d84444724a	Replaced use of the generic write_generic() helper with direct packet construction for selected PostgreSQL protocol messages to reduce overhead and improve performance.	5 months ago
René Cannaò	360646b7d5	Merge pull request #5165 from sysown/crash-sqlite-max-len processlist: Prevent crash due to SQLITE_TOOBIG	6 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
Rahim Kanji	91c674495a	Few fixes	6 months ago
René Cannaò	ecad6f9249	Merge pull request #5160 from sysown/v3.0_disable_pgsql_prometheus_5159 Separate Query Cache Metrics for MySQL and PostgreSQL & Disable Prometheus Metrics for PostgreSQL	6 months ago
René Cannaò	01862a247a	Merge pull request #5149 from sysown/v3.0_track_search_path_param_5148 Add search_path parameter to tracked ProxySQL variables list - PgSQL	6 months ago
Rahim Kanji	cb2062c1d1	Few fixes	6 months ago
Rahim Kanji	f88b781905	Removed pending_connect	6 months ago
Rahim Kanji	8f8a8c29e3	Code cleanup: Removed is_select_NOT_for_update from PostgreSQL modules	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
René Cannaò	e1b7afe282	Merge pull request #5099 from wazir-ahmed/clock-monotonic-raw Use `CLOCK_MONOTONIC_RAW` instead of `CLOCK_MONOTONIC`	6 months ago
René Cannaò	18b07a0066	Merge pull request #5120 from sysown/v3.0_clang_compilation_fix Fixed clang compilation	6 months ago
René Cannaò	9290a5ceec	Merge pull request #5124 from sysown/v3.0_postgres_query_logging_issue_5123 Added query logging support for PostgreSQL	6 months ago
Rahim Kanji	9b0366a89a	Improved PostgreSQL Logger	7 months ago
Rahim Kanji	a7df0d3b3c	Fixed clang compilation	7 months ago
Rahim Kanji	23a764eaac	Preserve implicit transactions with pipeline + FLUSH #5118 Previously, each extended-query block was terminated with a SYNC, which caused implicit transactions to commit prematurely. As a result, earlier write operations (INSERT/UPDATE/DELETE) could not be rolled back if a later statement in the same sequence failed. This change switches to libpq pipeline mode and replaces intermediate SYNC messages with FLUSH, ensuring that all client query frames execute as part of the same implicit transaction. A final SYNC is still issued to resynchronize the connection and make it safe for reuse in the pool.	7 months ago
Rahim Kanji	7d5fe54230	Refactor: unify result handling for Parse and Describe Previously, Parse and Describe each had their own query result handling paths. This duplicated a lot of logic and also failed to handle some cases correctly—for example, Notice messages returned by the server during extended-protocol queries. Keeping these separate paths would be hard to maintain and prone to bugs. The simple-query result handling is already mature, optimized, and covers all the necessary cases. Reusing it for Parse and Describe makes behavior consistent across simple and extended query flows, while also reducing duplicate code.	7 months ago
Wazir Ahmed	8d29742e20	`QueryInfo::end_time` should always be greater than or equal to `start_time` Signed-off-by: Wazir Ahmed <wazir@proxysql.com>	7 months ago
Rahim Kanji	9a5fa148c8	Inject implicit Sync if simple query arrives before extended query cycle is completed When a simple query arrives while extended query messages are pending, we now: - inject an implicit Sync, - process all extended query messages, - then execute the simple query, - and send ReadyForQuery only after the simple query completes.	7 months ago
Rahim Kanji	abd19113c0	Fix RequestEnd: avoid updating internal state when query failed on backend RequestEnd was applying state changes (session variable restore, rollback-to-savepoint, multiplexing toggle for temp tables/sequences) even when the query failed to execute on the backend connection. This caused internal state to diverge from the actual backend state. Fix: - Add success/failure flag to RequestEnd calls. - Restrict state-changing logic to Simple Query and Prepared Execute. - Ensure logic only runs when the query executed successfully on backend. This keeps internal state aligned with the backend connection state.	7 months ago
Rahim Kanji	96c989a854	* Replaced virtual RequestEnd method with CRTP (static polymorphism) * Removed multi_pkt from PgSQL_session	7 months ago
Rahim Kanji	7a1852fb92	Skip Describe Portal results unless client explicitly requests it PQsendQueryPrepared always emits Bind -> Describe Portal -> Execute, which led to RowDescription being included in the result set even when the client never sent a Describe message. This caused clients to receive row descriptions they did not request. Changes: - Skip including RowDescription when the client did not send Describe. - If the client explicitly sent Describe followed by Execute, continue to skip redundant execution of Describe but include RowDescription once. This ensures RowDescription is only sent when requested, aligning behavior with protocol expectations.	8 months ago
Rahim Kanji	9e4b76d6d1	* Refactored PgSQL_Session::handler___status_WAITING_CLIENT_DATA___STATE_SLEEP___PGSQL_QUERY_qpo. * Fixed a crash occurring during session destruction. * Query rules will now apply only to the first message in an extended query frame. * OK message will apply to execute message. * Query rewrite, error messages, and large packet handling will apply to parse message. * Added query processing support for the Bind message.	8 months ago
Rahim Kanji	2d569f3b95	Added support to terminate running queries on timeout	8 months ago
Rahim Kanji	4d195adc89	Renamed Multiplex status from MYSQL to PGSQL Renamed status to ssl_status Removed STATE_SLEEP_MULTI_PACKET from PgSQL session handler	8 months ago
Rahim Kanji	070d4ca18d	Added DEALLOCATE <stmt_name> and DEALLOCATE ALL support	8 months ago
Rahim Kanji	02eb58db79	Added SET statement tracking support	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	1bcd09044b	Refactor Connection Reset Handling * Introduced startup parameters in PgSQL_Connection (removed default session parameters from PgSQL_Session) * Startup parameters are populated during both frontend and backend connection creation * Parameters provided via connection options are set as startup parameters * Backend connection parameter handling updated: only critical variables are now set via connection options to prevent interference with DISCARD ALL during connection reset; remaining parameters will be applied using individual SET commands	8 months ago
Rahim Kanji	4ebff4c0cc	Added support for protocol-supplied (out-of-band) parameter typing (argument-based) * This parameter types will be part of hash calculation * Few refactoring and optimizations	9 months ago
Rahim Kanji	06383750b3	Fixed SonarQube warnings where applicable	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	3cff4f9dca	* Added sticky backend support for extended query frames: all messages in a single frame will now use the same backend connection. * Fixed few compilation warnings. * Removed AutoCommit relate code from PostgreSQL session.	9 months ago
Rahim Kanji	d5fc1fefff	Renamed pending_query to extended_query_frame Improved extended query frame handling	9 months ago
Rahim Kanji	8bb248cef5	Added Bind and Execute support	9 months ago

1 2 3

105 Commits (2fcc5729eec032a0e3d95a72fbdc08e7903940cc)