version
CRITICAL (2 rules)WARNING (2 rules)INFO
Rule IDs: ver_000, ver_001, ver_002, ver_003, ver_004
Overview
- Purpose
- Server product and release string reported by the instance (for example from
versionorversion_comment). Used for lifecycle and compatibility review; it is not configured withSET GLOBAL. - Dynamic (MySQL 8.4 reference)
- Not applicable — reported by the server.
- Default value
- N/A (read from the running server).
- Version and product notes
- Exact format depends on MySQL, MariaDB, or Percona Server build.
- Documentation
- Primary reference depends on product (MySQL, MariaDB, Percona, or OS documentation).
What is checked
Rules that reference this variable, with their severity and what each rule detects:
- INFO
ver_000: Keep your instance updated to the latest minor/patch version for security and performance improvements. - CRITICAL
ver_001: Upgrade to MySQL 8.4 LTS (supported until 2032) or MySQL 9.x Innovation track. - WARNING
ver_002: Update to the latest patch release of your current major version. - CRITICAL
ver_003: Upgrade to MariaDB 10.6 LTS (EOL Jul 2026), 10.11 LTS (EOL Feb 2028), or 11.4 LTS (EOL May 2029). - WARNING
ver_004: Switch to a MariaDB LTS branch: 10.6, 10.11, or 11.4 for long-term stability and support.
Tuning guidance
- Recommended actions:
- Keep your instance updated to the latest minor/patch version for security and performance improvements.
- Upgrade to MySQL 8.4 LTS (supported until 2032) or MySQL 9.x Innovation track.
- Update to the latest patch release of your current major version.
- Upgrade to MariaDB 10.6 LTS (EOL Jul 2026), 10.11 LTS (EOL Feb 2028), or 11.4 LTS (EOL May 2029).
- Switch to a MariaDB LTS branch: 10.6, 10.11, or 11.4 for long-term stability and support.
- Trade-offs: Running an end-of-life MySQL version means no security patches. Upgrading requires planning, testing, and possible application changes for deprecated features.
Example
Not applicable.