ProxySQL 3.0.8 Release Notes

Release date: 2026-04-25

ProxySQL 3.0.8 is a maintenance and feature release for the Stable Tier. It introduces two large new subsystems — MySQL session-variable tracking and PostgreSQL Cluster Sync — together with significant PostgreSQL improvements (per-server backend SSL parameters, backend-side SSL keylog, mid-transaction backend-death recovery, monitor scheduling fixes), MySQL protocol/auth fixes (zstd compression level decoupling, caching_sha2_password hex-rounds, MySQL 9.x charset handling), GTID wire-protocol enhancements, and a comprehensive code-quality and packaging modernization. macOS now compiles cleanly for development use.

Release commit: 6ef036a00c6f1dbcf3f27fe7f6e07f3211d7d6f8

Highlights

• MySQL Session-Variable Tracking: New mysql-session_track_system_variables mode (DISABLED / OPTIONAL / ENFORCED) lets ProxySQL stay aligned with backend-driven session-variable changes (system variables and state_change notifications) and route around servers that reject the configured set via per-server backoff (#5166).
• PostgreSQL Cluster Sync: First-class peer-to-peer cluster synchronization for the PgSQL admin surface — pgsql_query_rules, pgsql_servers (v2 + runtime), pgsql_users, pgsql_variables, and the new pgsql_servers_ssl_params — with runtime checksums, optional save-to-disk, and dedicated admin controls (#5297).
• Per-Server PgSQL Backend SSL: New admin table pgsql_servers_ssl_params brings per-backend CA / client cert+key / cipher / TLS protocol range / CRL configuration to PostgreSQL backends, closing the long-standing parity gap with mysql_servers_ssl_params (#5583).
• PgSQL Backend SSL Keylog: NSS-format keylog support, previously available for MySQL backends, is extended to PostgreSQL backends via a libpq patch (PQsetSSLKeyLogCallback). Existing admin-ssl_keylog_file now covers PgSQL backends transparently (#5567).
• PgSQL Mid-Transaction Backend-Death Recovery: When a PgSQL backend dies inside a transaction, ProxySQL now keeps the client session open, surfaces SQLSTATE 25P02 (in_failed_sql_transaction), and lets the application recover with ROLLBACK instead of having its connection torn down. Gated by pgsql-preserve_client_on_broken_backend_in_tx (default true) (#5654, #5659).
• Configurable MySQL zstd Compression Level: New mysql-zstd_compression_level variable (range 1–22, default 3) decouples zstd from mysql-protocol_compression_level, removing the v3.0.7 confusion where a single variable spanned two algorithms with very different level semantics (#5637).
• MySQL DNS Resolution Family: New mysql-resolution_family variable (system / ipv4 / ipv6, default system) makes backend hostname resolution deterministic on dual-stack hosts (#5554).
• Authentication: caching_sha2_password rounds field is now parsed as hexadecimal per the MySQL spec — fixes auth failure for accounts with rounds ≥ 10000.
• Greeting Capabilities Restored: Upper-word capability bits dropped by an earlier refactor are re-advertised in the MySQL greeting, restoring negotiation with clients that depend on those bits.
• macOS Build Support: ProxySQL now compiles cleanly on macOS (Apple Silicon and Intel) for development use; new on-demand CI-build-macos-* workflows produce per-tier tarballs (#5664).
• Packaging Pipeline: 156 on-demand per-distro × per-tier × per-variant Linux package workflows + 6 macOS workflows, all converging on a single canonical draft release per SHA via a race-tolerant find-or-create flow (#5662, #5666, #5668, #5671).

New Features

MySQL Session-Variable Tracking (#5166)

ProxySQL has long supported session-variable tracking by parsing SET statements and reapplying the captured values on backend swaps (the MySQL_Set_Stmt_Parser path). That approach is correct only for variable changes that flow through statements ProxySQL can parse; values changed by stored procedures, triggers, or anything that emits OK-packet session-state notifications without a matching parsed SET would drift between client and backend. This release enhances the existing mechanism by additionally tracking variables at the protocol level — enabling and consuming the MySQL server's own session_track_system_variables and session_track_state_change notifications — so the proxy stays correct in cases the parser cannot see.

The new mode-driven mechanism:

• New variable: mysql-session_track_system_variables — modes:
  • DISABLED (default) — preserves existing behavior; the hot-path read is gated so disabled deployments pay no overhead.
  • OPTIONAL — ProxySQL configures session_track_system_variables and session_track_state_change on backends, captures change notifications from OK packets, and reconciles client-side and server-side variable maps. If a backend rejects the configured set, ProxySQL marks that server with a per-server backoff (session_track_backoff_until) so subsequent connection attempts skip it for a window.
  • ENFORCED — same behavior as OPTIONAL, but additionally the client-side handshake preserves the EOF capability bit (and other capability advertising) so clients negotiating on those bits keep working through the proxy. This corrects an interaction discovered when enforcement is enabled.
• Variable changes that previously could only be propagated via MySQL_Set_Stmt_Parser are now also captured via backend notifications.
• Observability: misconfiguration and runtime backoff transitions are emitted via proxy_debug for diagnosis.
• Together with the new mode, the legacy field MySrvC::server_backoff_time was renamed to session_track_backoff_until to reflect its scope.

GTID Ranged Updates

A two-phase change to ProxySQL's GTID handling, coordinated with proxysql_mysqlbinlog:

• Phase 1 — Internal GTID model rework (#5224, #5557): gtid_interval_t is replaced by a proper Gtid_Interval / GTID_Set class hierarchy. Adding a new GTID to a GTID_Set now de-dupes and compacts overlapping intervals automatically, and intervals can be compared and merged. Internal-only refactor — no behavior change to ProxySQL on its own.
• Phase 2 — Wire-protocol ranged updates (96f1b414, 9f6751f, 23c153f, dca01d4, a95acd0): adds parsing for new I3= (single trxid range with UUID) and I4= (range without UUID) message types from proxysql_mysqlbinlog. Unknown message types now disconnect the binlog reader rather than silently parsing partial state. Updates GTID_Set formatting and includes unit tests for the wire parser (I1/I2/I3/I4) and for TrxId_Interval.
• Prepared-Statement min_gtid Preservation (0e5fd66): the min_gtid annotation on prepared statements is now preserved in first_comment_parsing mode so GTID-aware read-after-write routing works for prepared-statement traffic.

PostgreSQL Cluster Sync (#5297)

PostgreSQL gains its own peer-to-peer cluster-sync implementation, bringing PgSQL configuration to parity with MySQL cluster sync:

• Synchronized tables: pgsql_query_rules, pgsql_servers (both runtime and v2 layouts), pgsql_users, pgsql_variables, plus the new pgsql_servers_ssl_params.
• Runtime checksums for each module, with admin-visible diff/sync counters.
• Save-to-disk: synced peer state can be persisted via the same admin pipeline used for MySQL.
• Decoupled controls: PostgreSQL checksum/sync controls are independent of MySQL — disabling MySQL checksums no longer suppresses PgSQL diff propagation.
• Admin controls: new runtime/admin keys to view/toggle the PgSQL checksum, expose diffs-before-sync counters, and toggle save-to-disk behavior.
• Validator: integer validator added for PgSQL variables.
• Internally, the implementation uses a unified data-driven pull framework (a single get_peer_to_sync_variables_module() replaces the per-module functions) and an RAII memory-management framework, so the PgSQL sync paths share architecture with the MySQL ones.

Per-Server PostgreSQL Backend SSL Parameters (#5583)

New admin table pgsql_servers_ssl_params, mirroring mysql_servers_ssl_params:

• Schema keyed by (hostname, port, username) with an empty-username fallback row.
• Per-row columns: ssl_ca, ssl_cert, ssl_key, ssl_capath, ssl_crl, ssl_crlpath, ssl_cipher, ssl_protocol_version_range, comment.
• ssl_protocol_version_range accepts a range (TLSv1.2-TLSv1.3) or a single pin (TLSv1.3); ProxySQL maps it to libpq's ssl_min_protocol_version / ssl_max_protocol_version.
• Eliminates the previous limitation that all PgSQL backends shared the global pgsql-ssl_p2s_* settings, which made heterogeneous PgSQL fleets, per-tenant mTLS, and per-server CRLs impractical.
• Fully integrated into the PgSQL admin → runtime → connection → monitor pipeline.

PostgreSQL Backend SSL Keylog (#5567)

NSS-format keylog support is extended from MySQL backends to PostgreSQL backends:

• A small libpq patch adds PQsetSSLKeyLogCallback() (mirroring libpq's existing PQsslKeyPassHook pattern) and hooks it via SSL_CTX_set_keylog_callback() for every new SSL context.
• ProxySQL registers its existing keylog writer with libpq once at startup; this single registration covers all PgSQL backend connection paths (regular sessions, kill-query, monitor, query-tool, static harvester).
• No new admin variables — the existing admin-ssl_keylog_file covers PgSQL backends automatically. Operators can decrypt PgSQL backend traffic with Wireshark/tshark via the same workflow already used for MySQL.

PostgreSQL Mid-Transaction Backend-Death Recovery (#5654, #5659)

Two cooperating changes:

• Bug fix (#5654): when a PgSQL backend connection broke mid-transaction, ProxySQL would silently replay the failed statement on a fresh backend running it as autocommit. The client's next COMMIT then landed on a connection with no open transaction and PostgreSQL emitted only WARNING: there is no transaction in progress — never surfaced to the application. ProxySQL now correctly marks the transaction state unknown when is_connected() == false so the retry guard fires and the failure is propagated to the client. Pipeline-mode behavior is unchanged.
• New feature (#5659): rather than tearing the client session down (the strictly-correct-but-poor UX consequence of the above fix), ProxySQL synthesizes a Postgres-native ERROR 25P02 in_failed_sql_transaction plus a NoticeResponse carrying the backend's original message, then ReadyForQuery('E'). The client TCP stays open; libpq transitions to PQTRANS_INERROR; subsequent simple-query packets are short-circuited (ROLLBACK/ABORT clears the poisoned state, COMMIT/END is treated as Postgres natively does in an aborted transaction, anything else returns ERROR 25P02). Extended Query (P/B/D/C/E/Sync) while poisoned is rejected. Three new counters in stats_pgsql_global:
  • pgsql_tx_poisoned_total
  • pgsql_tx_poisoned_recovered_total
  • pgsql_tx_poisoned_rejected_statements_total
• Gated by pgsql-preserve_client_on_broken_backend_in_tx (bool, default true). Operators who rely on session termination as an app-layer signal can flip it off. Fallback to the pre-feature terminate-the-session path applies when the result-set transfer to the client has already started (too late to synthesize 25P02 mid-stream) or when the session is not in an explicit transaction.
• MySQL is not affected — the MySQL protocol caches SERVER_STATUS_IN_TRANS, so the underlying silent-replay hazard does not exist there.

PostgreSQL Monitor: Scheduler Clamp on Interval Change (#5614)

PgSQL_Monitor_scheduler_thread() previously cached next_<type>_at timestamps (one per check kind) computed from the prior interval. Setting a new interval via LOAD PGSQL VARIABLES TO RUNTIME had no effect until the already-scheduled (potentially long) cycle naturally elapsed — under the worst case, a fresh monitor_connect_interval=2000ms would not be honored for nearly two minutes if the previous interval was 120000 ms. The scheduler now detects a runtime variable refresh and clamps each next_<type>_at down to cur_intv_start + new_interval when the new value would schedule the next check sooner.

PostgreSQL CopyCmdMatcher Performance & Comment Handling (#5596)

• Fast-reject: a cheap strcasestr("COPY ") pre-check skips RE2 entirely for non-COPY queries (the previous code ran the full RE2 matcher on every query).
• Regex fix: the old regex used \s+ between COPY/FROM/STDIN, which broke on inline comments such as COPY /*c*/ t FROM /*c*/ STDIN when query_digests was disabled. The new regex tolerates intervening tokens via [^;]*?.
• Known limitation: with query_digests disabled, the matcher can still match COPY inside a string literal (e.g. SELECT 'COPY x FROM STDIN').

MySQL DNS Resolution Family (#5554)

New global variable mysql-resolution_family:

• Values: system (default, AF_UNSPEC — defers to OS resolver) / ipv4 (AF_INET) / ipv6 (AF_INET6).
• Plumbed through MySQL runtime variable storage with input validation and lowercase normalization for consistent persistence.
• Mapped directly into getaddrinfo() hints.ai_family while preserving existing AI_ADDRCONFIG behavior.
• Known limitation: applies to ProxySQL's DNS-cache resolution path. On a DNS-cache miss the hostname is passed directly to mysql_real_connect, which the MariaDB client library resolves with hardcoded AF_UNSPEC — the setting does not apply on that path. To ensure the setting is effective the DNS cache must be populated (the default behavior when monitor is active). PostgreSQL equivalent (pgsql-resolution_family) is planned in a follow-up.

Configurable MySQL zstd Compression Level (#5637)

ProxySQL 3.0.7 added zstd support but reused mysql-protocol_compression_level (range −1..9, intended for zlib) for both algorithms. Because zstd levels go up to 22, this made levels 10–22 inaccessible and the same numeric value meant very different ratios for the two algorithms. The new mysql-zstd_compression_level variable:

• Range 1–22 (clamped to ZSTD_maxCLevel()), default 3.
• Independent of mysql-protocol_compression_level (which now controls zlib only).
• No breaking change for existing deployments — the new default matches the previous implicit zstd behavior.

MySQL Greeting Capabilities Restored

A refactor in v3.0.7 (commit 8c6a6444d, "fix: support zstd compression in mysql84 TAP") inadvertently dropped four upper-word capability bits that the greeting used to hardcode, breaking negotiation with clients that depend on them. Specifically:

• CLIENT_MULTI_STATEMENTS
• CLIENT_MULTI_RESULTS
• CLIENT_PS_MULTI_RESULTS
• CLIENT_REMEMBER_OPTIONS

These are now restored via a local extended_capabilities path in the greeting builder, matching what real MySQL 8.x advertises. The mysql-enable_client_session_tracking variable that was added alongside this work has been reverted; the greeting fix itself is independent and is kept.

CACHING_SHA2_PASSWORD() SQL Function: Optional Rounds Argument (#5640)

The sqlite3-side CACHING_SHA2_PASSWORD() SQL function used by ProxySQL admin now accepts an optional rounds argument, so administrators can match a backend server's configured iteration count when generating cached hashes.

Bug Fixes (Core ProxySQL)

• caching_sha2_password rounds parsed as decimal, not hex (4e39f3b) — pre-fix, any account with rounds ≥ 10000 (since the field is stored as hex per MySQL spec) failed authentication. Now parsed as hex.
• MySQL 9.x charset handling in validate_charset (7c6f42b) — the pre-8.0 / 8.x discrimination compared server_version[0] to '8', so MySQL 9.x and later were treated as pre-8.0 and the safety branch fired for collations with id ≥ 255. The check now compares the major version numerically.
• GR Monitor: ignore cached ping state on first iteration (96c686d) — mysql_server_ping_log could carry stale "unpingable" entries from before monitor_GR_thread_HG was (re)started; with the cache filter applied on the very first cycle, find_resp_srvs() returned empty and the writer hostgroup stayed empty for an entire healthcheck_interval. The first iteration now probes all configured hosts unconditionally; the cache filter resumes from iteration two onward.
• GTID range validation (ae88c07) — tighter validation rejects malformed range inputs before they corrupt GTID_Set.
• GTID parser: NULL check after strchr() (04b258e) — defensive NULL check in the I-message parser avoids a potential crash on malformed proxysql_mysqlbinlog traffic. Authored by @wazir-ahmed.

Improvements

• PgSQL: deprecated MD5_* API replaced with EVP (9d8b7b0) — the PgSQL protocol's MD5 password hashing migrated from the deprecated OpenSSL MD5_* functions to the EVP interface; functionally equivalent, future-proofed against MD5_* removal in newer OpenSSL.
• Lint and static-analysis sweep (#5594) — clang-tidy + cppcheck pass touching ~100+ files: include guards renamed to PROXYSQL_*_H, reserved identifiers fixed (__var → var_), C-style NULL → nullptr, uninitialized members initialized in 8 classes, several memory-safety fixes (leak, dangling pointers, bounds), printf format/argument bugs corrected, and missing copy-operation deletions added in 15 classes.
• Compiler warnings eliminated (fe89811, 41956b8, 4810f1f) — additional lib-wide cleanup: macro redefinitions, member-init reordering, reserved identifiers in Base/PgSQL hostgroup headers.
• Default make goal: build_src (7a1d639) — top-level make no longer accidentally builds the first target; build_src is the explicit default.
• Removed vendored sqlite-rembed (#5616) — the experimental Rust-based extension that was permanently null-guarded at runtime is removed. With it goes the only consumer of rustc/cargo in the tree, so PROXYSQL31=1 and PROXYSQLGENAI=1 builds no longer require the Rust toolchain. sqlite-vec (the C-only sibling) is preserved unchanged.

Build, Packaging & CI

Build & Platform

• macOS build support (#5664) — sqlite3 shared-lib link, missing libtool, const-correct cmp() and TrxId_Interval comparators, removal of unnecessary -luuid, and OpenSSL link-line cleanup for Darwin. The codebase now compiles cleanly on macOS 13 (Intel) and macOS 14 (Apple Silicon) for development.
• No more Rust toolchain — see sqlite-rembed removal above; applies to all three tiers.

Packaging

• 156 on-demand Linux package workflows (#5662, #5666) — 13 distros × 3 tiers (stable, PROXYSQL31=1, PROXYSQLGENAI=1) × architectures, with -clang and -dbg variants on amd64. All workflow_dispatch-only.
• 6 on-demand macOS workflows (#5671) — macos-13 (Intel x86_64) + macos-14 (Apple Silicon arm64) × 3 tiers, producing proxysql-<tier-adjusted-version>-macos-<arch>.tar.gz (e.g. proxysql-3.0.8-<sha>-macos-arm64.tar.gz). Naming convention matches the Linux RPM/DEB.
• Race-tolerant draft release dedup (#5668) — all package workflows converge on a single canonical draft release per (SHA, tag) via a lowest-id-wins find-or-create loop, eliminating the proliferation of duplicate v3.0-head drafts that previously appeared.
• Aggregate CI-package-build upload pattern fix (subsumed by the above) — see also future cleanup since the new per-distro workflows make the aggregate redundant.

CI / Test Infrastructure (test-only changes — no end-user impact)

• ASAN unit-test coverage (#5618) — new CI-unit-tests-asan-coverage workflow runs unit tests under AddressSanitizer with gcov instrumentation.
• Unified CI rewire (#5598, #5602, #5604, #5595, #5590) — group callers rewired, zero-test safety net added, workflow_run chain PR-SHA fix, unittests caller decoupled.
• dbdeployer-based MySQL 8.4 / 9.0 / 9.5 infrastructures (#5469, follow-ups) — new dbdeployer-based standalone, GR, and binlog-reader infras for MySQL 8.4, 9.0, and 9.5; slimmed dbdeployer images (#5647) ~70–77% smaller. MySQL 5.7 single-instance infra (#5579) added for the new mysql56-single-g1 TAP group used by session-tracking tests.
• Test-set reorganization — legacy-g[1-5] test sets merged into mysql{84,90,95}-g[1-5]; pgsql-* tests dropped from MySQL groups.
• TAP linters (#5638, #5619, #5606) — groups.json format linter, orphaned-entry detection, and TAP-test static-analysis lint enforced on every PR.
• Flaky / deterministically-broken test fixes — test_flush_logs-t (#5611, replaced fixed sleeps with bounded polling), pgsql-ssl_keylog-t (#5612, fixed container-local path + NSS-label regex), read_only_actions_offline_hard (#5613, completed an incomplete hostgroup migration in TAP setup), pgsql-servers_ssl_params-t in-flight monitor drain (25c8fd1), and test_cluster_sync widened sync timeout (deb1cbe). These are TAP/CI fixes only — no end-user behavior change.
• MariaDB replication helper for binlog TAP tests (#5622) — replaces the external binlog reader binary with a helper using MariaDB replication functions for COM_REGISTER_SLAVE + heartbeat verification.

Project & Process

• Contributor License Agreement (#5650) — new .github/CLA.md (Apache-derived ICLA + CCLA, adapted for ProxySQL LLC) and CLA-assistant signing flow documented in CONTRIBUTING.md.
• Dependabot bumps (#5655, #5656) — python-dotenv 1.2.2 in MCP discovery agent scripts.

Contributors

ProxySQL is a community-driven project, and we are grateful to all the contributors who helped make this release possible. A special thank you to:

• @wazir-ahmed for MySQL session-variable tracking (#5166), GTID range parsing and unit tests, the GTID strchr NULL-check, and ENFORCED-mode capability preservation.
• @rahim-kanji for PostgreSQL Cluster Sync (#5297), the mid-transaction backend-death recovery (#5654, #5659), per-server PgSQL SSL parameters (#5583), PgSQL backend SSL keylog (#5567), the CopyCmdMatcher improvements (#5596), the PgSQL Monitor scheduler clamp (#5614), and the MD5→EVP migration.
• @proton-lisandro-pin for the initial GTID interval refactor that made ranged updates possible (#5224).
• @mirostauder for continued build system and distribution-support work.

We also thank everyone who reported bugs, tested experimental features, and provided feedback during this release cycle.

Hashes

The release commit is: 6ef036a00c6f1dbcf3f27fe7f6e07f3211d7d6f8

SHA256s:

9363ab729aa39f749fda74fc1c4ba7f99cb4bf909c8286f25a95c245432e46c4  proxysql-3.0.8-1-almalinux10-clang.x86_64.rpm
959c8cd59943be4466061720513761e314fb5d49189d70df492ca870f7695a69  proxysql-3.0.8-1-almalinux10.aarch64.rpm
ef8a6a4191473531fee6c4725d81a2c330c91b47b457d43ebdd0afb79ed4c7a7  proxysql-3.0.8-1-almalinux10.x86_64.rpm
43c7e79fb945c50ecc77f552e5e34873b9b05fb3a08f5b885146bef368ccd25d  proxysql-3.0.8-1-almalinux8-clang.x86_64.rpm
f3b29ae7951c9db6915e3ff9fece472cab22a422d195ea3f5fd753e7874c10fe  proxysql-3.0.8-1-almalinux8.aarch64.rpm
47aa0e5874c82884b5c87a0e42b314efa71f9626ceb40d5fb0f670509dd957a1  proxysql-3.0.8-1-almalinux8.x86_64.rpm
569969e7fca7aad317662a27d3d8e123d228811f823dcdec989de6ae8b8b5f5d  proxysql-3.0.8-1-almalinux9-clang.x86_64.rpm
c12a2d68770b96197b4dd6e6288fd0c997438d96c94ef2b32c0046d14ca12aee  proxysql-3.0.8-1-almalinux9.aarch64.rpm
628c86c90bfd09191ce1d6d680cdc208f898e6340f877db80d33478cb455abb7  proxysql-3.0.8-1-almalinux9.x86_64.rpm
62191cfd66d5753154b86c25d3bdceda19d8b603d594f3f9a33f701e42cf24ee  proxysql-3.0.8-1-centos10-clang.x86_64.rpm
02e2a89308e8b526987d29a1a2b1528cb7d859d2dc3900101c1f02f836d12429  proxysql-3.0.8-1-centos10.aarch64.rpm
f69107e7481270c9a969681f279080b5c464222823cc8094f170ca3dea0ee704  proxysql-3.0.8-1-centos10.x86_64.rpm
95075c9abd9fa667356c821dce4b22eb1d43d3c681bdcbc919eb948a90c59991  proxysql-3.0.8-1-centos9-clang.x86_64.rpm
d5b0304ea0a3a1958645f9e111263db67843601e9c951e8f38cf36570681c46c  proxysql-3.0.8-1-centos9.aarch64.rpm
37a3ae55e2a13b37a00e33d144d533a75a41a68b50ad3d734115b5fd3fea40e8  proxysql-3.0.8-1-centos9.x86_64.rpm
992b25a21545c7c07651eae37044087aee8cf9124cd8674380ab592a5b981b05  proxysql-3.0.8-1-dbg-almalinux10.x86_64.rpm
23d61d9daf847cebb25d909793fce9c2f5484daeebb6290df19d2b307caebba9  proxysql-3.0.8-1-dbg-almalinux8.x86_64.rpm
a523d95f13df3be17aee9a053536e684b21c847997d14ecf24cfe6723788be77  proxysql-3.0.8-1-dbg-almalinux9.x86_64.rpm
e1ce065820f3f209f760303620dee25c894ed166332d5b9de90102bc2d0c6071  proxysql-3.0.8-1-dbg-centos10.x86_64.rpm
23676f3eebb22f400b2bfc828ebc7784ecf7499c79bb138046d9d82fb9e7bae7  proxysql-3.0.8-1-dbg-centos9.x86_64.rpm
c1a5e05be64c8a0be714c1b00063e89a25fd75bd9f89608fccf0ae66fd666b96  proxysql-3.0.8-1-dbg-fedora42.x86_64.rpm
8d258d8fd2ef005206f77b3a3c3d3d44296128b55e41aab6bd74244c9cb88530  proxysql-3.0.8-1-dbg-fedora43.x86_64.rpm
16ce1331b2f805f7ba4d570c1f49b3aa0f800569e938ace413aa26f51864e226  proxysql-3.0.8-1-dbg-opensuse15.x86_64.rpm
7e1f3ebd1e871128cc36689df7cd063c0e6c8385f9058c9fe5cbf90ef532bd5c  proxysql-3.0.8-1-dbg-opensuse16.x86_64.rpm
55c02c11ded9ae2f815bcc7b7fb8a80f0872fdee864b0aa5ea4b23814ed562e7  proxysql-3.0.8-1-fedora42-clang.x86_64.rpm
81ed863e42b101bc9555747d8ead28ce2e8581c8ac9aee0aed563b4198dee425  proxysql-3.0.8-1-fedora42.aarch64.rpm
5575c3667ec140afe64b401c2e737bdab67ff46c6ef950fbc4b576adb09d4fe3  proxysql-3.0.8-1-fedora42.x86_64.rpm
399a8539bef419eb3de31347e890dcd8a2b9ff6ff305e4b8424bb3237f3c5206  proxysql-3.0.8-1-fedora43-clang.x86_64.rpm
dff9336e101f2b4112523d4d375101360b42b3009fff004b99a796e7d2474c9e  proxysql-3.0.8-1-fedora43.aarch64.rpm
1696fc56f5764c309c8d687387f477f261107e429a6008e85c7341cb35104e6c  proxysql-3.0.8-1-fedora43.x86_64.rpm
37acd9dc827257c1f79ef762d4eb40f2a99775e8d4a502b1da9dc95baa83ba55  proxysql-3.0.8-1-opensuse15-clang.x86_64.rpm
f72f0d304bf2968f882b901f494517c2e59f4c70b2b5b5adff98e2cd46388f6e  proxysql-3.0.8-1-opensuse15.aarch64.rpm
b8aa0b5cacda0d69526c7f6e0c297e3842731ccc6c7c79f3fb291c899a3b5fd6  proxysql-3.0.8-1-opensuse15.x86_64.rpm
4bd0f10ab834cc2520d9404aa1dc17f18c7640d61e5caa5243032de4d8543416  proxysql-3.0.8-1-opensuse16-clang.x86_64.rpm
e18b05514f47e1419f8cac6aa72f54872fe43b5fa26d4884539d253f077985f1  proxysql-3.0.8-1-opensuse16.aarch64.rpm
aae1f354433d5cee2b76d9f29f8933ea174120ca1652c7376be30d36fc73b9d9  proxysql-3.0.8-1-opensuse16.x86_64.rpm
9ecb2f79b56b7b6443070fbe713b04c85d1423e86ddca594d7d042709efd191d  proxysql_3.0.8-dbg-debian12_amd64.deb
e7aa01d79b2937d3942277aa0631972ae2f7c14717f5abf09f1f1c6fbc7efefc  proxysql_3.0.8-dbg-debian13_amd64.deb
67a0bf06c52e0c43d5caf81484333287966a9dd8fd6a45090ca63b9ab3fdfc0f  proxysql_3.0.8-dbg-ubuntu22_amd64.deb
4e7436387398ce00494f989fb95ee00a115dbd960727728b6e7d399452d46845  proxysql_3.0.8-dbg-ubuntu24_amd64.deb
db06c4a052683bb011a8c0ccdbb82d272971e0f4d59e3d068a79d51d23eda35d  proxysql_3.0.8-debian12-clang_amd64.deb
c1fca002d87afcaabdbb3d5bee25dbb046c0f1b15b241d9ddcd3935eef3bdf86  proxysql_3.0.8-debian12_amd64.deb
9f6a180dbd5d233a5d6e77379b94b3f266ef7c3514a4e84f736ec6ea04664cfe  proxysql_3.0.8-debian12_arm64.deb
109b3537d63d98d499791422fa0ef48d31e8564b76cb2d9b69c2793e8e6e0327  proxysql_3.0.8-debian13-clang_amd64.deb
3ab7effb838ab20f99e0148b9479be78d39efcd2697d0135bc9ae6c3ee7fb72c  proxysql_3.0.8-debian13_amd64.deb
d79455c8596a42777b7a7ff3936787e6311a51dc909dba4977535fddada95358  proxysql_3.0.8-debian13_arm64.deb
a9b16bb6bf5a9843366a951cca6b437b784ad1e9f3cbf337de8e7879e1cb3b5f  proxysql_3.0.8-ubuntu22-clang_amd64.deb
df33c0d8997d0f786adbd49ce17afa3206c0de15d5f6806331d2ea9a04a0084a  proxysql_3.0.8-ubuntu22_amd64.deb
c7858cf8c310212f8871cda49503600cf848f649be16894a958b7a702acf356c  proxysql_3.0.8-ubuntu22_arm64.deb
fd7c82ba9c9e475d43e2622974c077fa8b6fd94890bdfa4653cb043bf2357a90  proxysql_3.0.8-ubuntu24-clang_amd64.deb
10c5a924ff661325baf2bfc37313c4672619a940c5a6824722bb258ce45bcdc1  proxysql_3.0.8-ubuntu24_amd64.deb
b1f02a64f3f3629412ee6d3fad8de4f5c720b6fd20141b45f63353c43339dc55  proxysql_3.0.8-ubuntu24_arm64.deb