From c5efa9d5de9088ddd32e6a04dc72c6afa58152c4 Mon Sep 17 00:00:00 2001
From: Brian Devendorf <brian@brianjd.com>
Date: Sun, 31 Aug 2025 11:13:07 -0500
Subject: [PATCH] Correct Inaccurate Message for MariaDB

Fixes reporting issues with innodb_redo_log_capacity on MariaDB, where it does not exist.

Regression from pull request #849.
---
 mysqltuner.pl | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/mysqltuner.pl b/mysqltuner.pl
index d97406baf..82f126d12 100755
--- a/mysqltuner.pl
+++ b/mysqltuner.pl
@@ -6598,7 +6598,7 @@ sub mysql_innodb {
     # InnoDB Log File Size / InnoDB Redo Log Capacity Recommendations
     # For MySQL < 8.0.30, the recommendation is based on innodb_log_file_size and innodb_log_files_in_group.
     # For MySQL >= 8.0.30, innodb_redo_log_capacity replaces the old system.
-    if ( mysql_version_ge( 8, 0, 30 ) ) {
+    if ( mysql_version_ge( 8, 0, 30 ) && defined $myvar{'innodb_redo_log_capacity'} ) {
         # New recommendation logic for MySQL >= 8.0.30
         infoprint "InnoDB Redo Log Capacity is set to " . hr_bytes($myvar{'innodb_redo_log_capacity'});