proxysql · Issues· 1086 open

Connect timeout after ProxySQL start, during storm of backend connections (3.x only, not reproducible on 2.x)

TAP build and isolated test infra fail on arm64 build containers and macOS hosts

test(pgsql): regression test for poisoned-transaction recovery with JSON event logging (#6084)

PostgreSQL Prepared Statement Collision with ProxySQL 3.0.8

docker-base: stop hardcoding orchestrator-client amd64.deb

Pre-2018 open issues triage and cleanup

ProxySQL's PostgreSQL module rejects `Bind` messages that request **mixed per-column result formats** (some result columns text, some binary) with:

[DOCS/ENHANCEMENT] Clarify runtime_mysql_users desynchronization recovery & atomic purge flow during client handshake errors

Aurora monitor can remain permanently blind after a failover when use_ssl=1

Too many CLOSE_WAIT connections to backend mysql servers

connection_max_age_ms does not bound connection age: reset() restarts the age counter

[feature request] connection lifetime for backend connection

v4.0/MCP: LOAD MCP PROFILES TO RUNTIME silently drops target profiles, and runtime_mcp_target_profiles disagrees with list_targets

ProxySQL closes idle Sequel Ace frontend sessions after ~15 minutes although no matching timeout is configured

Add a query-rule action to switch a MySQL session to fast-forward mode