Pre-2018 open issues triage and cleanup

Real Triage of Pre-2018 Open Issues (updated 2026-07-07)

All issues created before 2018 that are still open (current count: 68).

Guiding rule from maintainer: Lack of activity on a feature request is not a reason for closure.

Closed in this 2026 triage round (per explicit "ok to close" + code verification): #35, #36, #132 (reopened per "keep unless experimental code removed"), #169, #238, #286, #400, #435, #574, #602, #622, #831, #862, #890, #932, #1019, #1040, #1116 and others from the lists.

See previous comments for per-issue evidence and code pointers (MySQL_Session.cpp, Admin_Handler.cpp, Query_Processor.cpp, monitor, etc.).

Current still-open pre-2018 issues (kept open per feedback or not yet reviewed for closure):

• #87 (2014-12-28 → 2019-09-06) implement SAVE MYSQL and LOAD MYSQL
• #132 (2015-01-11 → 2026-07-07) Implement text interface for Admin Module to support Admin commands
• #226 (2015-03-01 → 2015-03-01) Deprecate global variable mysql-server_capabilities
• #331 (2015-08-17 → 2015-08-17) Implement command SHOW GLOBAL VARIABLES LIKE
• #335 (2015-08-18 → 2015-08-18) Implement offline help system similar to mysqld
• #374 (2015-09-01 → 2015-09-01) Define a maximum QPS throughput per query
• #436 (2015-11-10 → 2025-08-11) Implement slow query logs
• #440 (2015-11-16 → 2024-11-27) Changes on mysql-interfaces shouldn't requires a restart
• #477 (2016-02-15 → 2026-01-01) Create new FLUSH command to remove OFFLINE servers from stats_mysql_connect
• #532 (2016-04-14 → 2018-07-28) reserved identifier violation
• #538 (2016-04-20 → 2016-04-20) Parse flagOUT in query comments
• #557 (2016-04-28 → 2025-08-11) Implement a command to kill at once all the backend connections
• #558 (2016-04-28 → 2025-08-11) Implement a command to kill at once all the frontend connections
• #560 (2016-04-28 → 2016-04-28) When a query timeouts it is not logged in stats_mysql_query_digest
• #569 (2016-05-17 → 2018-07-02) Release generic binaries in tarball format
• #597 (2016-06-19 → 2016-06-19) Debug mode query rewrite
• #616 (2016-07-19 → 2016-10-27) Admin: allows UPDATE/DELETE with ORDER BY and LIMIT
• #647 (2016-08-17 → 2024-06-25) Create a backup during downgrade
• #670 (2016-08-30 → 2016-08-30) Handling of connection attributes
• #697 (2016-09-15 → 2016-09-15) Backup hostgroups, and custom node monitoring
• #698 (2016-09-15 → 2021-10-28) Handler error "No database selected"
• #701 (2016-09-23 → 2016-09-23) Implement persistent connection
• #731 (2016-10-11 → 2016-10-11) feature request: include matched rule_id(s) in stats_mysql_query_digest
• #748 (2016-10-21 → 2016-10-28) Make the error log configurable and more readable.
• #753 (2016-10-24 → 2016-11-30) flush all infomation of tables stats.xxxx
• #783 (2016-11-04 → 2025-11-27) mysql_users doesn't seem to support host restrictions
• #806 (2016-11-26 → 2016-11-26) Export metrics on how many times connections are switch between main and au
• #807 (2016-11-26 → 2025-10-27) Track terminated connections
• #814 (2016-12-02 → 2017-01-26) feature request about users(fronted and backed)
• #853 (2016-12-23 → 2016-12-23) I can't decrease the value for "mysql-max_stmts_cache"
• #893 (2017-01-26 → 2023-06-21) don't break running queries till they finish - replication lag server offli
• #937 (2017-03-02 → 2017-04-21) Backend does not Return from OFFLINE_HARD when shutdown manually
• #941 (2017-03-06 → 2017-03-07) hostgroups, query rules and temporary tables
• #957 (2017-03-16 → 2019-03-27) Enhancement: Support for Stored Procedures SIGNALS
• #971 (2017-03-28 → 2025-03-07) [Feature] Implement a mechanism to automatically unshun nodes even if there
• #980 (2017-04-07 → 2024-12-19) mariadb: SHOW SLAVE STATUS vs SHOW ALL SLAVES STATUS
• #982 (2017-04-08 → 2017-04-08) Constraint violation in sharded sysbench transactions
• #983 (2017-04-09 → 2017-04-10) mysql-connect_retries_delay doesn't work
• #1000 (2017-04-19 → 2017-04-19) Filter ProxySQL error messages based on error code
• #1048 (2017-06-14 → 2025-09-18) Problem with "LAST_INSERT_ID()" returning 0
• #1071 (2017-06-23 → 2022-08-22) Feature request: Syslog option for query logging
• #1075 (2017-06-29 → 2020-12-07) Regex match when replace pattern and negate_match_pattern flag are set but
• #1078 (2017-07-02 → 2025-11-27) consul-template for proxysql - discussion
• #1105 (2017-07-21 → 2022-09-08) proxysql + MySQL WorkBench
• #1133 (2017-08-14 → 2017-08-14) Complete implementation of schema_locked
• #1134 (2017-08-14 → 2020-07-04) Support SELECT CONNECTION_ID
• #1135 (2017-08-15 → 2017-08-15) Support SELECT CURRENT_USER
• #1136 (2017-08-15 → 2017-11-26) Support for SHOW CHARSET and SHOW COLLATION
• #1139 (2017-08-15 → 2017-08-15) Support for SHOW ENGINES
• #1143 (2017-08-17 → 2017-08-18) Laravel can not call a procedure on proxysql
• #1149 (2017-08-22 → 2025-11-27) Add destination_schemaname to mysql_query_rules
• #1153 (2017-08-28 → 2017-09-20) User auth per source IP
• #1156 (2017-08-31 → 2018-03-18) Down mysql server is shown as online in ProxySQL
• #1170 (2017-09-11 → 2017-09-11) Query mirroring.
• #1171 (2017-09-11 → 2018-07-02) Help with mysql_query_rules
• #1193 (2017-09-30 → 2026-06-13) Extend ProxySQL to support PrestoDB Backend?
• #1225 (2017-11-07 → 2026-06-13) Forwarding connection to other proxysql servers
• #1250 (2017-11-17 → 2026-06-13) ProxySQL will never disable multiplexing if a persistent connection has use
• #1251 (2017-11-18 → 2026-06-13) Can't create more than max_prepared_stmt_count statements
• #1261 (2017-11-28 → 2026-06-13) Unable to Parse Query: Report it as a bug
• #1263 (2017-11-29 → 2026-06-13) Adjust default for mysql-shun_recovery_time or mysql-connect_timeout_server
• #1273 (2017-12-05 → 2026-06-13) Make CLIENT_MULTI_STATEMENTS configurable
• #1274 (2017-12-06 → 2026-06-13) Run a script when an event happens.
• #1293 (2017-12-20 → 2026-06-13) proxysql memory usage grown unlimit
• #1294 (2017-12-20 → 2026-06-13) ProxySQL 1.4.4 Unable to connect with laravel
• #1296 (2017-12-21 → 2026-06-13) ClickHouse Grant Option
• #1298 (2017-12-22 → 2026-06-13) Support regex matching extra information in first comment
• #1303 (2017-12-27 → 2026-06-13) [WARNING] Detected broken idle connection

Explicit "still relevant" / keep open per latest feedback: #87, #132, #226, #331, #335, #374 (old PR exists), #436, #440, #477, #532 (VALID - verify keyword work), #538, #557, #558, #560 (verify timeout+digest), #569, #597, #616, #647, #980, #1071, #1105, #1133, #1134/1135/1136/1139 (still relevant, "perhaps" needs check), #1149

"ok to close" already processed above.

No mass closure of stale feature requests. Each closure had explicit sign-off + evidence.