91 Commits (9f30d85e10c5db24c041cb50584fdb856479e26e)

Author	SHA1	Message	Date
Rahim Kanji	9c0e14a5d1	Replace rand() with lock-free Xoshiro128++ PRNG	4 months ago
Rahim Kanji	1a48aadf5e	Code cleanup	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
Rahim Kanji	e744c2bbb7	Optimize transaction command parsing to avoid unnecessary tokenization ... Previously, the parser always tokenized the full command, even when we only needed to check whether it was a transaction command. Now, it first extracts the first word to determine relevance and performs full tokenization only when necessary.	5 months ago
René Cannaò	413b0121a1	Merge pull request #5146 from sysown/v3.0_parameter_status_case_sensitive_issue_5145 ... Fix incorrect ParameterStatus key casing for DateStyle, TimeZone, and IntervalStyle	6 months ago
Rahim Kanji	dc6db358f4	Few fixes	6 months ago
Rahim Kanji	03b63f6857	Fix ParameterStatus capitalization for DateStyle, TimeZone, and IntervalStyle ... These parameters use capitalized names in PostgreSQL for historical reasons. ProxySQL now sends them using canonical capitalization to ensure client compatibility.	6 months ago
Rahim Kanji	9cb605f4fb	Replaced rand() with random()	6 months ago
Rahim Kanji	3a46324d5d	Fixed Debug logs	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	692109f965	Fixed typo	7 months ago
Rahim Kanji	205f970ffa	Append NoData for DESCRIBE(Portal) on SET/RESET/DISCARD/DEALLOCATE	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
Rahim Kanji	31503d42e3	Merge remote-tracking branch 'Master/v3.0_issue_5100' into v3.0_extended_query_protocol_phase_2	7 months ago
Rahim Kanji	43e5b55c1c	Added integer_datetimes in ProxySQL startup parameters status, hardcoded to on. ... Added scram_iterations in ProxySQL staup parameters status, hardcoded to 4096 (SCRAM_SHA_256_DEFAULT_ITERATIONS)	7 months ago
Rahim Kanji	8a3bab5002	Ensure consistent handling of NoData packets in PQsendQueryPrepared ... The PQsendQueryPrepared function transmits the sequence BIND -> DESCRIBE(PORTAL) -> EXECUTE -> SYNC. However, libpq does not indicate whether the DESCRIBE PORTAL step produces a NoData packet for commands such as INSERT, DELETE, or UPDATE. In these cases, libpq returns PGRES_COMMAND_OK, whereas SELECT statements yield PGRES_SINGLE_TUPLE or PGRES_TUPLES_OK. This update explicitly appends a NoData packet to the result in order to provide consistent behavior across query types.	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	4d3dc7b7e3	Fixed DISCARD ALL tag	8 months ago
Rahim Kanji	070d4ca18d	Added DEALLOCATE <stmt_name> and DEALLOCATE ALL 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	5e30bef674	Few fixes	9 months ago
Rahim Kanji	703a5f35f5	Added stats_pgsql_prepared_statements_info table	9 months ago
Rahim Kanji	06383750b3	Fixed SonarQube warnings where applicable	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	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	d3592020ac	* Created a separate file for Extended Query messages to reduce clutter in PgSQL_Protocol. ... * Moved get_uint32be() and get_uint16be() to gen_utils.h * Split PgSQL_*_Message into distinct Message and Data components.	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	8bb248cef5	Added Bind and Execute support	9 months ago
Rahim Kanji	4d0618c296	Added Close statement handling	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	190e369658	Added Transaction State flag in SQLite3_to_Postgres	11 months ago
Rahim Kanji	c2f2ae5aa4	* Updated code to use pgsql_tracked_variables[idx] consistently, removing ... direct usage of pgsql_tracked_variables[idx].idx. This change improves consistency and reduces potential human error. * Fixed some warning	1 year ago
Rahim Kanji	b8ffb7d56e	Fixed connection parameter validation	1 year ago
Rahim Kanji	db442ba8cf	Treat client_encoding as normal server parameter/variable. ... Optimized RESET ALL command handling. Few optimizations. Code cleanup	1 year ago
Rahim Kanji	fbb9500cb9	Refactored connection parameters ... * Accept all parameters sent by the client, mirroring PostgreSQL's permissive handling. * Validate and apply parameters only after successful authentication. This avoids wasting resources on invalid connections.	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	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	c7960f836b	Added Parameter Status	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	f0316c7d50	Since notices can reorder packets, it is important to account for this when calculating the result set size	1 year ago
Rahim Kanji	f16f553995	Added PostgreSQL notice handler	1 year ago
Rahim Kanji	395a977e68	Merge branch 'v3.0'	1 year ago
Rahim Kanji	551aeed43e	Improved COPY OUT format extraction	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	616a8e0e23	Implemented handling of COPY OUT ... Added threshold checks to manage result size	1 year ago