1852 Commits (71e8a2e8d5a71ff052b6ef3d9c1731401d422cc7)

Author	SHA1	Message	Date
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.	6 months ago
Rahim Kanji	be2ae45950	Merge branch 'v3.0' into 'v3.0_extended_query_protocol_phase_2'	6 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.	6 months ago
Rahim Kanji	96c989a854	* Replaced virtual RequestEnd method with CRTP (static polymorphism) ... * Removed multi_pkt from PgSQL_session	6 months ago
Rahim Kanji	8d8577b0ad	Ensure PgSQL_Threads_Handler and PgSQL_HostGroups_Manager objects are released when ProxySQL shuts down or restarts.	6 months ago
Rahim Kanji	c7ce5a8298	Ensure PgSQL_Threads_Handler and PgSQL_HostGroups_Manager objects are released when ProxySQL shuts down or restarts.	6 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.	6 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.	6 months ago
Rahim Kanji	42400a1e8a	Commented multi_pkt code	6 months ago
René Cannaò	b5fa8ca1ae	Merge pull request #5044 from sysown/v3.0_extended_query_protocol ... PostgreSQL's Extended Query Protocol Support in ProxySQL [WIP]	6 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.	6 months ago
Rahim Kanji	2d569f3b95	Added support to terminate running queries on timeout	6 months ago
Rahim Kanji	58eac30ff3	Fixed SSL STATUS in PgSQL_Data_Stream	6 months ago
Rahim Kanji	0ddc6e9b93	* Implemented status tracking for LOCK TABLE and pg_advisory_xact_lock, with automatic reset on transaction end ... * Added tracking for pg_advisory_lock, with status reset only on pg_advisory_unlock_all * Implemented support for CREATE SEQUENCE and CREATE TEMP SEQUENCE, with reset on DISCARD SEQUENCES * Added handling for CREATE TEMP TABLE, with reset triggered by DISCARD TEMP	7 months ago
Rahim Kanji	a29eaf1eb2	Moved warning_in_hg from Base_Session to MySQL_Session	7 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	7 months ago
Rahim Kanji	441504190d	Moved sess_STMTs_meta and SLDH from Base_Session to MySQL_Session	7 months ago
René Cannaò	afb1865107	Merge pull request #5043 from sysown/v3.0-pgsql_mon_table_fix ... Fix table definition for 'pgsql_replication_hostgroups'	7 months ago
Rahim Kanji	070d4ca18d	Added DEALLOCATE <stmt_name> and DEALLOCATE ALL support	7 months ago
Rahim Kanji	099597d2d8	Added client_close_all	7 months ago
Rahim Kanji	02eb58db79	Added SET statement tracking support	7 months ago
Rahim Kanji	ce94a7080a	Merge branch v3.0_session_param_reset_connection into v3.0_extended_query_protocol	7 months ago
Rahim Kanji	249b3d8725	* Replace C-style array with std::array in PgSQL_Connection ... * Nulling startup_parameters[i] in ~PgSQL_Connection after freeing	7 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.	7 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	7 months ago
Rahim Kanji	344ba25777	Add Watchdog PROXYSQLTEST covering MySQL and PgSQL threads	7 months ago
Rahim Kanji	28931cd00d	* Replaced malloc with std::vector for safer memory management. ... * Marked functions ref_count_client and ref_count_server as noexcept since standard exceptions are not being handled and application crashes are acceptable in such cases.	7 months ago
Rahim Kanji	3619fa5d21	Added pgsql-max_stmts_per_connection variable	7 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	7 months ago
Rahim Kanji	a8a2799187	Improved locks	7 months ago
Rahim Kanji	703a5f35f5	Added stats_pgsql_prepared_statements_info table	7 months ago
Rahim Kanji	b989fc2bad	Refined Bind Message parameter format, value handling, and result format iterator	7 months ago
Rahim Kanji	06383750b3	Fixed SonarQube warnings where applicable	7 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	7 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	7 months ago
Javier Jaramago Fernández	b7b4864729	Fix table definition for 'pgsql_replication_hostgroups' ... - Reduce 'check_type' range to uniquely supported check ('read_only'). - Added table upgrade procedure. - Fixed missing space in table definition (display for '\G').	8 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	8 months ago
Rahim Kanji	7cde1dcad6	Added comments	8 months ago
Rahim Kanji	f9448948cd	Set end state for fetch result to indicate that it originates from a simple query or statement execution	8 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.	8 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.	8 months ago
Rahim Kanji	d5fc1fefff	Renamed pending_query to extended_query_frame ... Improved extended query frame handling	8 months ago
Rahim Kanji	f350102f72	Code cleanup	8 months ago
Rahim Kanji	8bb248cef5	Added Bind and Execute support	8 months ago
Javier Jaramago Fernández	25d5681c61	Fix potential overflow for 'sqlite3_status' memory metrics ... The previous call have been replaced by 'sqlite3_status64' when querying 'SQLITE_STATUS_MEMORY_USED' to avoid potential integer overflows.	8 months ago
Rahim Kanji	4d0618c296	Added Close statement handling	8 months ago
Rahim Kanji	a741598a8d	Added Describe message handling	8 months ago
Javier Jaramago Fernández	6f2798abe0	Fix memory leak in 'ProxySQL_Admin::stats___mysql_global' - Closes #4976 ... The resource leak was associated to prepared statements (sqlite3_stmt). Since the detection of these leaks is tricky, because the resources held by 'SQLite3' never lose their references, a helper type ('stmt_unique_ptr') and a safer variation for 'prepare_v2' have been introduced. This helper type should automatically handle the lifetime of the statements, avoiding these kind of leaks in the future. The non-safe alternative has been flagged as 'deprecated', so it can be easily identified in later refactors or slowly removed during development.	8 months ago
Rahim Kanji	2a9f67295f	Removed warning tracking code from PgSQL_Connection	8 months ago
Rahim Kanji	58c18846c8	Added set_is_client method	8 months ago