7272 Commits (c2f2ae5aa4c85e6a72daa3700f7bc72724beda2e)

 

All Branches   

Search

Author	SHA1	Message	Date
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	11 months ago
Rahim Kanji	4c918490a4	Added TAP test ... Note: - Using libpq to test ProxySQL's handling of undocumented parameters isn't possible, as libpq enforces a strict subset of PostgreSQL connection parameters as per the official documentation, rejecting any undocumented parameters. However, actual PostgreSQL servers accept additional parameters (e.g., extra_float_digits) and apply them at the connection/session level. To test this behavior, a raw socket is used to connect to a ProxySQL server and send custom built messages to communicate with ProxySQL. It currently works with plain text password authentication, without ssl support. - Failure due to an invalid parameter returned by the PostgreSQL server, differs from ProxySQL's behavior. PostgreSQL returns an error during the connection handshake phase, whereas in ProxySQL, the connection succeeds, but the error is encountered when executing a query. This is behaviour is intentional, as newer PostgreSQL versions may introduce new parameters that ProxySQL is not yet aware of.	11 months ago
Rahim Kanji	b8ffb7d56e	Fixed connection parameter validation	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ò	8f51df70b7	Merge pull request #4799 from sysown/v3.0_session_parameter_tracking ... Session parameter/variable tracking for PostgreSQL - v3.0	12 months ago
Miro Stauder	fdd744adbd	Create CI-3p-aiomysql.yml ... Signed-off-by: Miro Stauder <miro@proxysql.com>	12 months ago
René Cannaò	a9bdf5462a	Merge pull request #4859 from sysown/v3.0-4856 ... Prevent unnecessary VACUUM executions for SQLite3 stats database - Closes #4856	12 months ago
Javier Jaramago Fernández	42ae3d5e3c	Increase verbosity for tap util 'get_proxysql_cpu_usage'	12 months ago
Rahim Kanji	9f7cb598f7	Added pgsql_variable_validate_maintenance_work_mem_v3, it now supports decimal values too	12 months ago
Rahim Kanji	19297e37d6	Modified TAP test description	12 months ago
Rahim Kanji	f9232ae50d	Merge remote-tracking branch 'Master/v3.0' into v3.0_session_parameter_tracking	12 months ago
Rahim Kanji	0e19af4897	Added TAP test	12 months ago
Rahim Kanji	c5fb8da375	Improved Session parameter value validator	12 months ago
Rahim Kanji	94399faaf9	Added 1 and 0 in bool validation	12 months ago
Rahim Kanji	055e748673	Fixed DateStyle Validator ... If the provided datestyle includes both style and order, ensure both values are valid.	12 months ago
Rahim Kanji	9388d5dc15	Fixed IntervalStyle parameter values	12 months ago
Rahim Kanji	6603d48bb0	Optimized and simplified PostgreSQL variable Validator	12 months ago
René Cannaò	4c7558889c	Merge pull request #4814 from sysown/v3.0_compression_test_fix ... Move setting of compression level to correct place in the tap test	12 months ago
René Cannaò	f27aa6fa64	Merge pull request #4842 from sysown/v3.0_collation_255 ... Fix issue #4841	12 months ago
Javier Jaramago Fernández	2c7b9847f6	Optimize 'stats_mysql_global' generation with prepared statements ... Measurements ('perf') revealed that 'prepare' from 'execute' where taking roughtly half the execution time of the queries used for table generation.	12 months ago
Javier Jaramago Fernández	9e941854c3	Replace table based 'VACUUM' for SQLite3 'stats' database ... Introduced generic approach based on the potential benefits for 'VACUUM' over the 'stats' database instead of the previous selective, table based, approach.	12 months ago
Javier Jaramago Fernández	a4d4e3639e	Fix format for 'proxy_debug' message	12 months ago
René Cannaò	4f878a44cf	Merge pull request #4852 from sysown/v3.0-4839 ... Ignore tracking of session_track_system_variables	12 months ago
Rahim Kanji	07badd8eff	Fixed PostgreSQL set statement parser	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
René Cannaò	d963232ce0	Ignore tracking of session_track_system_variables ... Adding variable session_track_system_variables to `ignore_vars` Also added `@@session.` and `@@global.` in the parser for SET statements (parse1v2) See issue #4839	12 months ago
Rahim Kanji	5475e00972	Updated SET statement parser ... * Simplifyed regular expression, specifically targeting PostgreSQL SET statements.	12 months ago
Rahim Kanji	41206d2ee7	Added enable_nestloop parameter	12 months ago
Javier Jaramago Fernández	4d99265a46	Merge pull request #4833 from sysown/v3.0-flush_debug ... PROXYSQL FLUSH LOGS forces debug database flush	1 year ago
Javier Jaramago Fernández	8bb1f9cd76	Improve impl for 'get_fmt_time' tests helper function	1 year ago
Javier Jaramago Fernández	e6f0fab208	Add identifier to warmup queries for 'test_query_rules_fast_routing_algorithm-t.cpp' ... More queries were received during testing ('stats' user) that matched the previous check criteria. Warmup queries should now be uniquely identified with the test itself.	1 year ago
René Cannaò	e0e4d0652b	Fix issue #4841 ... Incorrectly attempt to use a collation with id larger than 255 during backend handshake Problem: When creating a backend connection, if the frontend connection has configured a collation with id larger than 255 (for example using SET NAMES utf8mb4 COLLATE utf8mb4_0900_as_ci; , ProxySQL may try to create a new connection using such collation. The problem is that at protocol level, during handshake only 1 byte can be used to configure the collation. That means that if ProxySQL sets a collation greater than 255 , only the less significant byte is used. Therefore even if ProxySQL believes that the backend connection will use the specified collation, mysql_real_connect() is using a different collation. For example, using collation 305 will lead to use collation 49 (305-256). Solution: When a collation id greater than 255 is detected, the default collation for that character set is used. ProxySQL will later issue a SET NAMES ... COLLATE to address the mismatch.	1 year ago
René Cannaò	a9a3583957	Update issue templates	1 year ago
Javier Jaramago Fernández	eb11af42fc	Change default behavior for test utils 'get_proxysql_cpu_usage' ... By default 'get_proxysql_cpu_usage' now uses the currently configured interval for measuring system CPU usage ('admin-stats_system_cpu'). A parameter still allows to use a custom configured interval, but since maximum resolution is used for testing environments, the default value should normally be the one used.	1 year ago
Javier Jaramago Fernández	9e1999e55c	Fix default argument for 'get_fmt_time' impl	1 year ago
Javier Jaramago Fernández	a06595820a	Fix typo in 'test_auth_methods' info logging	1 year ago
Javier Jaramago Fernández	6e932c82de	Replace failure with warning in 'test_auth_methods' ... Previously 'test_auth_methods' flagged a current ProxySQL limitation regarding auth full-handshakes with an error. This has been replaced with a warning until fixed.	1 year ago
Javier Jaramago Fernández	1da6dfec29	Remove unnecessary/unused utils from tests	1 year ago
Javier Jaramago Fernández	a247d13d76	Several fixes for 'test_query_rules_fast_routing_algorithm-t.cpp' ... - Fixed issue with SQLite3 helper functions. Invalid use of 'sqlite3_step' lead to fixing issue in ProxySQL itself. - Fixed logic issues on tests checking duplicated conditions. - Improved waiting logic checking for new entries in debug database. - Added new utility functions for SQLite3 databases access (debug database) following MySQL utilities conventions. - Simplified interface in several utilities functions with new, and more explicit naming convention.	1 year ago
Javier Jaramago Fernández	611ea853ed	Add new per-query received 'proxy_debug' entry ... This new entry allows to associate session, thread and query being processed, and offers some extra details about the query itself.	1 year ago
Javier Jaramago Fernández	b27d1a92b1	Fix missing error handling for 'sqlite3_step' on 'SQLite3_result' ... Error handling for 'sqlite3_step' should be performed in a similar fashion as for 'sqlite3_exec'. Not handling these potential errors could result in invalid empty/incomplete resultsets when reading from the internal SQLite3 databases.	1 year ago
Javier Jaramago Fernández	cff7eaea69	Fix usage of 'sqlite3_step' for test utils 'sqlite3_execute_stmt'	1 year ago
Javier Jaramago Fernández	e346b15bdf	Expose 'get_fmt_time' function in 'tap.h' interface	1 year ago
Rahim Kanji	e0ced2e14c	Fixed extra_float_digits variable position	1 year ago
Rahim Kanji	5d7d459ee2	Now supports timezone values in the format 00:00	1 year ago
Rahim Kanji	427f20072b	Tracking new variables ... allow_in_place_tablespaces enable_sort extra_float_digits synchronous_commit	1 year ago
Rahim Kanji	a084f0f2ed	Fixed SET parser	1 year ago
Rahim Kanji	465852eb0e	Added t and f, representing the true and false flags, respectively.	1 year ago
Rahim Kanji	b368b281ee	Added pg_advisory_xact_lock* detection	1 year ago