proxysql

Commit Graph

Author	SHA1	Message	Date
Rene Cannao	ef351a6a67	test/groups: drop reg_test_3992 from mysql8x/95 groups The reg_test_3992_fast_forward_malformed_packet-{t,pymysql,mysqlsh} tests hard-code MariaDB-specific users (mariadbuser, mariadbuserff) that are provisioned only by infra-{mariadb10,dbdeployer-mariadb10}. The mysql84-g2, mysql90-g2 and mysql95-g2 groups don't include a MariaDB infra, so the test fails immediately with "Access denied for user 'mariadbuserff'". Restrict the three variants to legacy-g2 and the mysql-* knob-variant g2 groups (which inherit the legacy infra layout including MariaDB).	1 month ago
Rene Cannao	174c5bda20	test: expand zstd_compression_level test with MySQL 8.4 C API and timing benchmark The existing test only verified admin variable behavior (default, range, independence). It did not prove that ZSTD compression was actually active on the wire. Two new test variants address this: MariaDB connector path (mysql-zstd_compression_level-t): - Tests 1-9: unchanged (variable defaults, range validation, independence) - Tests 10-11: use mysql CLI via execvp with --compression-algorithms=zstd and --zstd-compression-level={3,19}. Each call spawns a new process (= new connection). Verifies CONNECTION_ID() retrieval and large resultset transfer. Skipped if mysql CLI lacks zstd support. MySQL 8.4 connector path (mysql-zstd_compression_level_libmysql-t): - Tests 1-9: same as MariaDB path - Test 10: establishes a ZSTD connection using mysql_options( MYSQL_OPT_COMPRESSION_ALGORITHMS, "zstd") and prints mysql_thread_id() without running any query. - Test 11: timing benchmark proving compression is active. Creates a query rule (rule_id=1, cache_ttl=60000) to cache all SELECTs, then runs a 576-row resultset query 1000 times on a plain connection and 1000 times on a ZSTD level 22 connection. ZSTD level 22 is extremely CPU-intensive: observed 40122ms vs 858ms (46.7x ratio). A ratio >= 3x proves compression is really running on the client<->ProxySQL link. Other changes: - MySQL_Protocol.cpp: simplify redundant clamping to a simple cast (the variable is already validated at SET time) - Makefile: add build rule for _libmysql variant linking against MySQL 8.4 connector - groups.json: register _libmysql variant for mysql84/90/95-g1 - CLAUDE.md: update testing section with CI script usage and DO NOT list	1 month ago
Rene Cannao	4631b1f466	fix: clean groups.json diff — only add mysql-zstd_compression_level-t entry	1 month ago
Rene Cannao	6dae8d125f	test: add TAP tests and housekeeping for mysql-zstd_compression_level - New test mysql-zstd_compression_level-t.cpp: validates default value, range enforcement (1-22), rejection of 0 and 23, independence from mysql-protocol_compression_level, and functional compressed connection. - Register mysql-zstd_compression_level-t in groups.json (same groups as mysql-protocol_compression_level-t). - Add variable visibility check to reg_test_2793-compression-t.cpp. - Add unit test binary pattern to .gitignore.	1 month ago
Rene Cannao	a0f685b998	fix: reformat groups.json to one-line-per-entry and add --fix to linter groups.json was reformatted with multi-line arrays by a recent merge, breaking the one-line-per-test convention documented in README.md. Changes: - Reformat groups.json to canonical format (one line per test, compact arrays, sorted keys, space before colon). - Add --fix mode to lint_groups_json.py that auto-reformats the file in-place, preventing this class of issue in the future.	1 month ago
Rene Cannao	d212102ce5	fix(tests): drop pgsql-* tests from mysql{84,90,95}-g[1-5] Follow-up to `4534e5b4d` (merge legacy-g[1-5] into mysql{84,90,95}-g[1-5]). The previous merge was over-inclusive: legacy-g* contains PostgreSQL tests (named 'pgsql-' or 'pgsql_' or '_pgsql_') that exercise ProxySQL's PostgreSQL front-end against the docker-pgsql16-single backend. Those tests don't care which MySQL version is also present, and the mysql{84,90,95} groups' infras.lst only lists infra-dbdeployer-mysqlXX — no PostgreSQL backend is brought up. So in myrun3 the merged pgsql tests failed (no backend) or hung until the per-group timeout (test_ffto_pgsql_concurrent-t). Removed 153 group memberships (pgsql-containing test names) from mysql{84,90,95}-g[1-5]. Safety check confirmed: no pgsql-containing test was in mysql-g before the merge, so this revert is scoped exactly to memberships the merge added. New sizes: legacy mysql84 mysql90 mysql95 g1 87 78 72 78 g2 43 45 45 45 g3 40 40 40 40 g4 94 61 61 61 g5 5 6 6 6 Net result vs pre-merge (pre-4534e5b4d): - mysql84-g1 back to 78 (same as pre-merge) - mysql90-g1 up from 16 to 72 (the non-pgsql legacy tests; +56) - mysql95-g1 back to 78 (same as pre-merge) - g2 / g3 / g5 unchanged from pre-merge for 84/95, mysql90-g* gets a few non-pgsql additions - g4 keeps the non-pgsql portion of the legacy merge (61 vs 60) Legacy-g[1-5] are untouched — pgsql tests remain where they belong. check_groups.py reports 385/385 registered, no orphans.	1 month ago
Rene Cannao	4534e5b4dc	feat(tests): merge legacy-g[1-5] test sets into mysql{84,90,95}-g[1-5] Every TAP test in legacy-gN is now also a member of mysql84-gN, mysql90-gN, and mysql95-gN (N=1..5). No tests removed from any group; legacy-g[1-5] keeps its existing membership intact. Rationale: the legacy group covers the MySQL 5.7 / MariaDB 10 / PgSQL / ClickHouse matrix, but many of its TAP tests are not inherently tied to MySQL 5.7 — they exercise ProxySQL behavior that should also hold against modern MySQL backends (8.4, 9.0, 9.5). Running them against those newer servers widens the matrix and catches 9.x-specific regressions in tests that weren't previously in a 9.x group. Mechanical merge via a walk over groups.json: for each test: for N in 1..5: if 'legacy-gN' in memberships: add 'mysql84-gN', 'mysql90-gN', 'mysql95-gN' if absent 224 new memberships added. Per-bucket union size (i.e. now a superset of legacy-gN): g1: legacy=87 mysql84=93 mysql90=87 mysql95=93 g2: legacy=43 mysql84=45 mysql90=45 mysql95=45 g3: legacy=40 mysql84=40 mysql90=40 mysql95=40 g4: legacy=94 mysql84=96 mysql90=96 mysql95=96 g5: legacy=5 mysql84=7 mysql90=7 mysql95=7 Verified as supersets (every test in legacy-gN is present in mysql{84,90,95}-gN). check_groups.py reports 385/385 tests registered, no orphans. Expect new 9.x-specific failures to surface when the mysql{90,95}-g* groups run these newly-inherited legacy tests — they're likely to hit the same family of mysql_native_password / caching_sha2_password issues we've already been working through in the sibling PR threads. Those will be triaged as they appear.	1 month ago
Rene Cannao	7eee687415	feat(tests): mirror mysql84-g[2-5] test sets into mysql90-g[2-5] Populates mysql90-g2 through mysql90-g5 with the same test assignments as mysql84-g2..5, matching the structure already applied to mysql95. Adds 147 group memberships, all targeting existing tests. mysql84-g2: 42 → mysql90-g2: 42 mysql84-g3: 40 → mysql90-g3: 40 mysql84-g4: 60 → mysql90-g4: 60 mysql84-g5: 5 → mysql90-g5: 5 mysql90-g1 intentionally left as the existing 16-test shared subset (still matches mysql91-g1 / mysql92-g1 / mysql93-g1). If you want g1 expanded to mysql84-g1 parity later (78 tests), it's a one-line follow-up. Fixes the runaway "TIMEOUT" seen in multi-group runs that included mysql90-g[2-5]: the tester would previously fall back to running all 325 tests when a group had no members (see separate commit that eliminates that fallback). check_groups.py still reports 385/385 registered, no orphans.	2 months ago
Rene Cannao	efa7922d01	feat(infra): add dbdeployer-based MySQL 9.0/9.5 binlog-reader infras Mirrors the existing infra-dbdeployer-mysql84-binlog layout (3-node replication + proxysql_binlog_reader on GTID ports 6020/6021/6022) for MySQL 9.0 and 9.5. Group replication binlog variant not requested; skipped. New infrastructures: test/infra/infra-dbdeployer-mysql{90,95}-binlog/ Hostgroup PREFIX assignment: mysql90-binlog PREFIX=37 (WHG/RHG/BHG/OHG = 3700/3701/3702/3703) mysql95-binlog PREFIX=38 (3800/3801/3802/3803) MySQL tarballs (x86_64 glibc2.17 variants, same as the standalone 9.x infras): mysql-9.0.1-linux-glibc2.17-x86_64.tar.xz mysql-9.5.0-linux-glibc2.17-x86_64.tar.xz Dropped the `-c mysql_native_password=ON` dbdeployer flag and the `IDENTIFIED WITH 'mysql_native_password'` clause, same as the other 9.x infras, since the plugin isn't usable on MySQL 9.x servers. Group wiring (test/tap/groups/): mysql{90,95}-binlog/ — env.sh + infras.lst, mirroring mysql84-binlog/ groups.json: registered mysql90-binlog-g[12] and mysql95-binlog-g[12] mirroring mysql84-binlog-g[12] exactly (g1=3 tests, g2=1 test). check_groups.py reports 385/385 registered. KNOWN LIMITATION — proxysql_binlog_reader v2.3 cannot authenticate: Smoke test of mysql90-binlog confirmed 3-node replication deploys cleanly and users replicate, but the binlog reader processes fail to start with: Could not mysql_real_connect(): Authentication plugin 'caching_sha2_password' reported error: Authentication requires secure connection. : 2061 Root cause: the bundled proxysql_binlog_reader v2.3 supports only -h/-u/-p/-P/-l/-L options — no SSL, no --get-server-public-key. MySQL 9.x's default caching_sha2_password requires either SSL or a preconfigured RSA public key, neither of which the reader can provide. mysql_native_password isn't a workable escape hatch on 9.x either: the .so still ships in the tarball but `INSTALL PLUGIN` fails with "Can't find symbol '_mysql_plugin_interface_version_'" — it's kept as a client library stub only. Resolution requires either (a) a newer proxysql_binlog_reader that speaks caching_sha2_password or supports SSL, or (b) SSL wrapping at the container level. Neither change is part of this commit; flagging here so the limitation is visible when the tests start failing under mysql{90,95}-binlog-g[12]. MySQL 8.4 binlog flow is unaffected.	2 months ago
Rene Cannao	f07859fd40	feat(tests): mirror mysql84-g[1-5] test sets into mysql95-g[1-5] Every TAP test currently executed against mysql84-g[1-5] is now also executed against the corresponding mysql95-g[1-5] group. Same 5-bucket split, same assignment per bucket: mysql84-g1: 78 → mysql95-g1: 78 mysql84-g2: 42 → mysql95-g2: 42 mysql84-g3: 40 → mysql95-g3: 40 mysql84-g4: 60 → mysql95-g4: 60 mysql84-g5: 5 → mysql95-g5: 5 total: 225 total: 225 Rationale: validates the full 8.4 test surface on MySQL 9.5, which is the whole point of adding the 9.x infras — different MySQL major versions catch different regressions (e.g., mysql_native_password removal in 9.0). Group Replication variants (mysql-gr-g) are intentionally out of scope for now. Scripted via a simple walk over groups.json: for each entry containing mysql84-gN, add mysql95-gN if missing, then re-sort. Verified: - 209 new memberships added (225 target - 16 already existing from the earlier mysql95-g1 seeding) - check_groups.py reports 385/385 tests registered, no orphans - per-bucket counts now match mysql84-g[1-5] exactly	2 months ago
Rene Cannao	de9e73cb5f	feat(infra): add dbdeployer-based MySQL 9.0/9.3/9.5 standalone and GR infras Mirrors the existing mysql84 / mysql84-gr layout (single-container dbdeployer sandboxes) for MySQL 9.0, 9.3, and 9.5 — both standalone replication and Group Replication variants. New infrastructures: test/infra/infra-dbdeployer-mysql{90,93,95}/ — standalone replication (3 nodes) test/infra/infra-dbdeployer-mysql{90,93,95}-gr/ — Group Replication (3 nodes, single-primary) Hostgroup PREFIX assignment (continuing the existing convention): mysql90 PREFIX=31 (WHG/RHG/BHG/OHG = 3100/3101/3102/3103) mysql93 PREFIX=32 (3200/3201/3202/3203) mysql95 PREFIX=33 (3300/3301/3302/3303) mysql90-gr PREFIX=34 (3400/3401/3402/3403) mysql93-gr PREFIX=35 (3500/3501/3502/3503) mysql95-gr PREFIX=36 (3600/3601/3602/3603) MySQL 9.x tarballs (via dbdeployer downloads get-unpack) use glibc2.28 (9.x no longer ships glibc2.17 bundles): mysql-9.0.1-linux-glibc2.28-x86_64.tar.xz mysql-9.3.0-linux-glibc2.28-x86_64.tar.xz mysql-9.5.0-linux-glibc2.28-x86_64.tar.xz MySQL 9.x compatibility notes: - mysql_native_password was removed in MySQL 9.0. Dropped both the -c mysql_native_password=ON dbdeployer flag and the IDENTIFIED WITH 'mysql_native_password' clause from CREATE USER / ALTER USER; users now use the server default (caching_sha2_password). ProxySQL may need SSL to authenticate to 9.x backends because caching_sha2_password requires either SSL or a preconfigured RSA key. This is left to follow-up tuning — flagging here for visibility. Group wiring (test/tap/groups/): mysql{90,93,95}/ — env.sh + infras.lst + setup-infras.bash + pre-proxysql.bash (no-op) mirror mysql84/ exactly, only the infra/group names differ mysql{90,93,95}-gr/ — env.sh + infras.lst + pre-proxysql.bash mirror mysql84-gr/; pre-proxysql.bash uses docker exec to configure ProxySQL with GR fallback HGs + users + rules groups.json: registered mysql95-g1 and mysql95-gr-g1 (16 tests each), identical test sets to the existing mysql93-g1 / mysql93-gr-g1 entries. check_groups.py reports 385/385 tests registered, no orphans. No changes touching existing infras; only new files + groups.json append. Validated with `python3 test/tap/groups/check_groups.py`.	2 months ago
Rene Cannao	3babaada88	fix: remove stale gtid_utils_unit-t from groups.json This test was removed in `06b6343dc` and replaced by gtid_set_unit-t and gtid_trxid_interval_unit-t. The merge with v3.0 accidentally restored the old entry.	2 months ago
Rene Cannao	6f5cf1f169	fix: sort groups.json keys after v3.0 merge	2 months ago
René Cannaò	732a65da5d	Merge branch 'v3.0' into fix/groups-json-orphaned-entries Signed-off-by: René Cannaò <rene@proxysql.com>	2 months ago
Wazir Ahmed	1e069fbc11	Merge 'v3.0' into feature/gtid-range-update	2 months ago
Rene Cannao	30e86ae04d	fix(tests): resolve 3 additional TAP test failures - Fix INFRA_LOGS_PATH in infra-mysql57-binlog/.env: removed INFRA_LOGS_PATH=./logs which overrode the proper default from docker-compose-init.bash, causing logs to be written inside test/infra/ instead of ci_infra_logs/ and never cleaned up - Increase PostgreSQL max_connections to 120 (from default 100) in docker-pgsql16-single and infra-pgsql17-repl configs to prevent connection slot exhaustion during monitor SSL tests - Skip session_track_gtids test cases in set_testing-240-t when running against MariaDB, which doesn't support this variable (issues #2134, #3059)	2 months ago
Rene Cannao	98083cdf0f	fix: resolve 4 TAP test failures in multi-group runs - set_testing-240-t: Fix crash (json type_error.302) when MySQL returns NULL variable values or fails the session_variables query. Add null guards in parseResult() and all implicit std::string conversions. - Add show_compatibility_56=ON to MySQL 5.7 configs so querying performance_schema.session_variables works reliably. - test_gtid_forwarding-t: Move from legacy-g5 to legacy-binlog-g1 (requires infra with session_track_gtids=OWN_GTID configured). - test_binlog_reader-t: Create own GTID query rules for sbtest8 instead of relying on pre-existing infra rules that may be deleted. - test_ffto_pgsql_error_stats-t: Remove from mysql84-g4 group (no PostgreSQL backend available in mysql84 infrastructure).	2 months ago
Wazir Ahmed	9757835a5f	Merge branch 'v3.0' into fix-fc-parsing	2 months ago
Wazir Ahmed	0f1aa30f4c	TAP: Test `min_gtid` annotation in prepare statements Signed-off-by: Wazir Ahmed <wazir@proxysql.com>	2 months ago
Rene Cannao	f606f1ba84	fix: sort groups.json entries alphabetically	2 months ago
Rene Cannao	80ff2242e6	merge: resolve v3.0 conflict and add pgsql_servers_ssl_params cluster sync v3.0 added pgsql_servers_ssl_params table. Integrate into pgsql cluster sync path: - Add CLUSTER_QUERY_PGSQL_SERVERS_SSL_PARAMS to Admin_Handler interception block alongside other pgsql cluster queries - Add ssl_params fetch query to pull_pgsql_servers_v2_from_peer - Add update_pgsql_servers_ssl_params() for applying synced data - Update convert_pgsql_servers_resultsets to handle 5 result sets - Include ssl_params in v2 checksum computation (4 tables)	2 months ago
René Cannaò	7f14beedc1	Merge pull request #5583 from sysown/v3.0_pgsql_ssl_backend_5582 Per-server SSL parameters for PostgreSQL backends	2 months ago
René Cannaò	1a8e4ed918	Merge pull request #5567 from sysown/v3.0_pgsql_sslkeylog_5281 Add SSL/TLS traffic decryption for PostgreSQL backend connections	2 months ago
René Cannaò	b771e4f6eb	Merge branch 'v3.0' into v3.0_ci_min_proxysql_version_5561 Signed-off-by: René Cannaò <rene@proxysql.com>	2 months ago
René Cannaò	f8dcf88bc2	Merge branch 'v3.0' into fix/postgresql-cluster-sync_2 Signed-off-by: René Cannaò <rene@proxysql.com>	2 months ago
René Cannaò	7ce2043b61	Merge branch 'v3.0' into v3.0-ci_84_mysql84 Signed-off-by: René Cannaò <rene@proxysql.com>	2 months ago
René Cannaò	93eabfc7bc	fix: address code review issues in PostgreSQL cluster sync - Fix fetch_and_store incrementing success counter on failure - Fix sqlite3_stmt leak in pull_pgsql_variables_from_peer (use RAII) - Convert get_peer_to_sync_pgsql_query_rules and _servers_v2 to unified framework delegates (fixes atomic data race on .load()) - Merge dual scan loops in set_checksums to respect enabled_check - Remove spurious "deprecated" label from new checksum_pgsql_variables - Replace sprintf with snprintf in pgsql diffs_before_sync getters - Fix indentation on cluster_pgsql_variables blocks - Fix TAP plan mismatch: replace MYSQL_QUERY with inline mysql_query - Fix trivially-true table accessibility assertions - Add mysql_close on failed connect in test - Move test_cluster_sync_pgsql-t to legacy-g5 group	2 months ago
Rene Cannao	9671a414a3	ci: comprehensive CI workflow and infrastructure fixes Workflow trigger chain fix: - All 24 test workflows now trigger on CI-builds completion instead of CI-trigger completion, ensuring build artifacts are available before tests start New test group workflows: - Add CI-legacy-g1, CI-legacy-g3, CI-legacy-g5 - Add CI-mysql84-g1 through CI-mysql84-g5 - All use the generic ci-taptests-groups.yml reusable workflow groups.json linter: - Add lint_groups_json.py enforcing compact one-line-per-entry format - Add CI-lint-groups-json.yml workflow triggered on groups.json changes - Reformat groups.json to comply with documented format Makefile fixes: - Fix $(error) call with unescaped ')' that broke all docker-compose builds since Release 3.0.8 - Fix CURVER extraction regex to handle 'v' prefix from git describe CI-taptests-pgsql-cluster rewrite: - Replace old jenkins-build-scripts with Unified CI infrastructure - Use ensure-infras.bash + run-tests-isolated.bash Infrastructure improvements: - Add --hostname test-runner to test-runner container for cross-container DNS resolution - Pass TAP_PGSQL_SYNC_REPLICA_PORT through to test container - Default TAP_PGSQL_SYNC_REPLICA_PORT=6042 when cluster nodes active	2 months ago
Rene Cannao	f2ed9436ce	fix: reformat groups.json to compact one-line-per-entry style The merge resolution used json.dump with indent=4 which broke the required format (one entry per line, compact arrays). Reformat to match the convention documented in test/tap/groups/README.md.	2 months ago
Rene Cannao	47758a468d	merge: resolve groups.json conflict with v3.0 Take v3.0's groups.json as base (legacy-gN naming, mysql84-gN groups, new test entries) and add test_cluster_sync_pgsql-t from this branch. Drop duplicate pgsql_admin_metacmds-t (already exists as pgsql-admin_metacmds-t in v3.0).	2 months ago
Rahim Kanji	4e23078db3	test: rename pgsql servers SSL params TAP test and register tests in groups.json Renames test/tap/tests/pgsql-pgsql_servers_ssl_params-t.cpp to pgsql-servers_ssl_params-t.cpp to drop the duplicated "pgsql-" prefix, updates the @file header to match, and registers both the integration test and the existing pgsql_servers_ssl_params_unit-t in test/tap/groups/groups.json so CI actually runs them. The integration test joins the same group set used by other PgSQL admin/SSL tests (legacy-g4 and the four mysql--g4 variants); the unit test joins unit-tests-g1 alongside the other pgsql__unit-t entries.	2 months ago
Wazir Ahmed	0e5fd66d46	Preserve prepared statement `min_gtid` in `first_comment_parsing` mode Issue --- When `first_comment` parsing runs before query rule processing, query rules can strip the `min_gtid` annotation during `STMT_PREPARE`. As a result, `STMT_EXECUTE` can run without the original `min_gtid` constraint. Refs --- - Commit - `1c25787b88` - https://github.com/sysown/proxysql/issues/5384#issuecomment-4137207612 Fix --- - Store `min_gtid` by frontend `client_stmt_id` in `MySQL_STMTs_local_v14` and restore it during `STMT_EXECUTE` using the client statement handle. - Add TAP test to cover the case of `[first_comment_parsing=1 + prepared_stmt + min_gtid + query_rewrite]` Signed-off-by: Wazir Ahmed <wazir@proxysql.com>	2 months ago
Rene Cannao	3296ed5a07	Moving test_cluster_sync_mysql_servers-t from legacy-g3 to legacy-g5	2 months ago
Rene Cannao	fe5a819051	Add 3 missing tests to groups.json Register newly compiled test binaries that were missing from groups.json, causing check_groups.py to block CI runs: - gtid_server_data_unit-t → unit-tests-g1 - test_ffto_mysql_errors-t → legacy-g4, mysql84-g4 - test_ffto_pgsql_error_stats-t → legacy-g4, mysql84-g4	2 months ago
René Cannaò	3659ba85fb	Merge branch 'v3.0' into advisory/com-stmt-send-long-data-fix-1 Signed-off-by: René Cannaò <rene@proxysql.com>	2 months ago
Rene Cannao	151169da9b	Fix COM_STMT_SEND_LONG_DATA short packet handling	2 months ago
René Cannaò	b94c855d4c	Merge branch 'v3.0' into advisory-fix-1 Signed-off-by: René Cannaò <rene@proxysql.com>	2 months ago
René Cannaò	fa6ebcdcc9	Merge commit from fork Fix PROXY protocol v1 address overflow	2 months ago
René Cannaò	419cd7608b	Merge commit from fork Fix COM_STMT_CLOSE short packet handling	2 months ago
René Cannaò	7a574a537a	Merge commit from fork Validate COM_CHANGE_USER packet bounds	2 months ago
Rene Cannao	307d70acb9	Add unit tests for GTID wire protocol parsing (I1/I2/I3/I4) Tests read_next_gtid() by buffer-stuffing, covering: - ST= bootstrap with single trxids and ranges - I1/I2 single trxid messages - I3/I4 range-based messages - I1 rejects range input (atoll parses only first number) - Unknown message type sets active=false and returns false - read_all_gtids() stops processing on unknown message - Empty buffer and incomplete message edge cases - Mixed message sequence with full GTID state verification	2 months ago
Rene Cannao	cbc50ebf8a	ci: add dedicated CI workflow and groups.json entry for pgsql cluster sync test Register test_cluster_sync_pgsql-t in groups.json (default-g3) so it is picked up by CI-taptests-groups and passes check_groups.py validation. Add CI-taptests-pgsql-cluster.yml as a standalone workflow that runs only the PostgreSQL cluster sync TAP test, triggered after CI-trigger or via workflow_dispatch.	2 months ago
Rahim Kanji	e7ee68dda5	Add SSL/TLS traffic decryption for PostgreSQL backend connections (#5281 ) Extends the existing NSS keylog-based SSL decryption to PostgreSQL backend connections by patching libpq with a global PQsetSSLKeyLogCallback() API. When admin-ssl_keylog_file is configured, TLS secrets from all PgSQL backend SSL handshakes are written to the keylog file in NSS Key Log Format, enabling traffic decryption with Wireshark/tshark. Approach: - Patch libpq with global callback following the PQsslKeyPassHook pattern - Single startup call covers all backend paths (regular, monitor, kill, harvester) - No new admin variables — existing admin-ssl_keylog_file covers PgSQL backends - Zero changes to ProxySQL PgSQL connection code Includes 9 integration tests (pgsql-ssl_keylog-t) and user guide updates.	2 months ago
Rahim Kanji	625e068412	Add @proxysql_min_version tag support for version-aware test execution Skip tests that require a newer ProxySQL version than the one being tested, preventing false-positive CI failures across v3.0.x/v3.1.x/4.0.x branches. Tagged 19 FFTO/TSDB tests (>=3.1) and 46 GenAI/MCP/AI tests (>=4.0) in groups.json. Tests without a tag run on all versions.	2 months ago
Rahim Kanji	6090537bd1	Merge remote-tracking branch 'v3.0' into v3.0-ci_84_mysql84	2 months ago
Rahim Kanji	af445f9405	Move cluster TAP tests from legacy-g3 to legacy-g5 Move test_cluster1-t, test_cluster_sync_mysql_servers-t, and test_gtid_forwarding-t to legacy-g5	2 months ago
Rene Cannao	b2f4b4f9a0	Fix crash when COM_BINLOG_DUMP received with idle backends from other hostgroups (#5556 ) When a session has backend connections to multiple hostgroups and receives COM_BINLOG_DUMP, GPFC_Replication_SwitchToFastForward() transitions the session to FAST_FORWARD mode but only manages the active backend. Idle backends from other hostgroups remain in the session's mybes array with async_state_machine==ASYNC_IDLE. If MySQL's wait_timeout closes one of these idle connections, the resulting POLLIN event causes handler() to be called with ASYNC_IDLE, which has no case in the switch and hits assert(0). Fix: Clean up idle backends from other hostgroups during the FAST_FORWARD transition in GPFC_Replication_SwitchToFastForward(). These connections will never be used again, so they are destroyed immediately. Includes a regression test (test_binlog_dump_multi_backend_crash-t) that: - Sets up two hostgroups with query rules routing SELECTs to reader HG - Creates backend connections to both hostgroups on one session - Sends COM_BINLOG_DUMP to enter FAST_FORWARD mode - Waits for wait_timeout to close the idle backend - Verifies ProxySQL does not crash	2 months ago
Rahim Kanji	0b0e634f0f	Add test_cluster_sync-t to mysql84-g5 group	2 months ago
Wazir Ahmed	06b6343dca	gtid: Update unit test for `GTID_Set` and `TrxId_Interval` Signed-off-by: Wazir Ahmed <wazir@proxysql.com>	2 months ago
Rahim Kanji	bf85d1735a	Remove pgsql FFTO tests from mysql84-g4	2 months ago

1 2 3 4

188 Commits (ee6d4e506ac47a9ef69b60efa5ddfc9cde2cd71d)