73 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	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	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	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	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	070d4ca18d	Added DEALLOCATE <stmt_name> and DEALLOCATE ALL support	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	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	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	06383750b3	Fixed SonarQube warnings where applicable	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
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	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	8bb248cef5	Added Bind and Execute support	8 months ago
Rahim Kanji	4d0618c296	Added Close statement handling	8 months ago
Rahim Kanji	a741598a8d	Added Describe message handling	8 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.	8 months ago
Rahim Kanji	026f458f7c	Removed last_insert_id from PostgreSQL modules	9 months ago
Rahim Kanji	979b3a81f4	Added PgSQL_ExplicitTxnStateMgr in session ... Dump transaction state in proxysql internal session output	10 months ago
René Cannaò	6df3d6b84b	Merge pull request #4899 from sysown/v3.0_refactor_connection_info_param ... Refactor PostgreSQL Connection-Level Parameters Handling	11 months ago
Rahim Kanji	db442ba8cf	Treat client_encoding as normal server parameter/variable. ... Optimized RESET ALL command handling. Few optimizations. Code cleanup	11 months 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.	11 months ago
René Cannaò	2551d350e9	Port to 3.0 of in-memory query logging ... See #4713 for further details	12 months 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.	12 months ago
Rahim Kanji	40be1158c2	Finally removed PgSQL_Connection_Placeholder class	1 year ago
Rahim Kanji	570e62b618	Removed MySQL Prepare Statement residual code	1 year ago
Rahim Kanji	a22936164b	Removed psql from PgSQL_Connection_Placeholder ... Removed dead code Removed MySQL Prepare Statement related code lib/PgSQL_Session.cpp # # Untracked files: # .gitattributes # .vs/ # PR_proxysql_postg.txt # include/query_cache - Copy.hpp # lib/Query_Cache - Copy.cpp # tash qqq # test/tap/tests/pgsql-basic_tests-t - Copy.cpp # test/tap/tests/pgsql-connection_test-t.cpp # test/tap/tests/pgsql-set_parameter_test-t.cpp #	1 year ago
Rahim Kanji	bcc20f8214	Moved few members and methods to PgSQL_Connection ... Removed deadcode	1 year ago
Rahim Kanji	87838bec14	Refactored get_default_session_variable	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	06e496b7c3	Added tracking of parameters: ... * client_encoding/names * datestyle * timezone/time zone * standard_conforming_strings	1 year ago
Rahim Kanji	f33fd02c37	Add COPY ... FROM STDIN detection regex	1 year ago
Rahim Kanji	b906c08992	Added dynamic fast forward support	1 year ago
Rahim Kanji	e64a4349d4	Few fixes	1 year ago
Rahim Kanji	79c7f13768	Clean up	1 year ago
René Cannaò	d4bd93672e	Merge pull request #79 from sysown/v2.x_refactore_query_processor ... Refactored Query Processor [WIP]	1 year ago
Rahim Kanji	e723082a1b	Refactored Query Processor Architecture ... - Introduced separate query processors for MySQL and PostgreSQL. - Removed unnecessary GTID logic from `PgSQL_Session`. - Added a command counter for PostgreSQL queries. - Refactored `Query_Processor` to serve as a base class containing core functionalities applicable to both MySQL and PostgreSQL. Changes: - Removed GTID-related code from `PgSQL_Logger` and `PgSQL_Session`: - bool with_gtid; - char gtid_buf[128]; - int gtid_hid; - Added new PostgreSQL-specific tables: - `pgsql_query_rules`, `pgsql_firewall_whitelist_rules`, `pgsql_query_rules_fast_routing` - `runtime_pgsql_query_rules`, `runtime_pgsql_firewall_whitelist_rules`, `runtime_pgsql_query_rules_fast_routing` - Added PostgreSQL-related variables: pgsql_thread___commands_stats pgsql_thread___query_digests pgsql_thread___query_digests_lowercase pgsql_thread___query_digests_no_digits pgsql_thread___query_digests_replace_null pgsql_thread___query_digests_normalize_digest_text pgsql_thread___query_digests_track_hostname pgsql_thread___query_digests_keep_comment pgsql_thread___query_digests_max_digest_length pgsql_thread___query_digests_max_query_length pgsql_thread___query_digests_grouping_limit pgsql_thread___query_digests_groups_grouping_limit pgsql_thread___enable_load_data_local_infile pgsql_thread___auditlog_filename pgsql_thread___auditlog_filesize pgsql_thread___eventslog_filename pgsql_thread___eventslog_filesize pgsql_thread___eventslog_default_log pgsql_thread___eventslog_format pgsql_thread___firewall_whitelist_errormsg pgsql_thread___firewall_whitelist_enabled pgsql_thread___query_processor_iterations pgsql_thread___query_processor_regex	1 year ago
René Cannaò	b64b087aab	Some code cleanup	1 year ago
René Cannaò	115eef2ea3	Some code cleanup	1 year ago
Javier Jaramago Fernández	25c6cf9dff	Fix 'nlohmann::json' type forwarding	1 year ago
Rahim Kanji	745449fcbc	Removed Client_Session.h and Client_Session.cpp	2 years ago
Rahim Kanji	5bf827d8e4	Removed type selector	2 years ago
Rahim Kanji	fb0d8c0b69	Merge remote-tracking branch 'remotes/Master_POSTGRES/v2.x_postgres' into v2.x_postgres_backend ... Conflicts: lib/PgSQL_HostGroups_Manager.cpp lib/PgSQL_Thread.cpp	2 years ago
Rahim Kanji	880d654011	Changing database on the same connection is not supported in PostgreSQL. If a connection with a different database is needed, a new connection will be created; otherwise, a connection with the same database (and username) will be selected from the connection pool.	2 years ago
Rahim Kanji	058be0d9ae	* Reset the connection if there is a mismatch between client and server ... session variables. * Changing the user on the same connection is not supported in PostgreSQL. If a connection with a different username is needed, a new connection will be created; otherwise, a connection with the same username will be selected from the connection pool. * Added RESET SESSION timeout.	2 years ago