summaryrefslogtreecommitdiff
path: root/mysql-test/suite/innodb/r/monitor.result
diff options
context:
space:
mode:
authorMarko Mäkelä <marko.makela@mariadb.com>2022-02-22 18:56:21 +0200
committerMarko Mäkelä <marko.makela@mariadb.com>2022-02-22 18:56:21 +0200
commit934b2d605ec15322f2a5052ebb90e116bce8aaaa (patch)
tree416cd42cf54efe9d4ba9f68989de30e006e7b378 /mysql-test/suite/innodb/r/monitor.result
parent30b036d7290ee115b0f5ec350796c92cc1942046 (diff)
downloadmariadb-git-934b2d605ec15322f2a5052ebb90e116bce8aaaa.tar.gz
MDEV-27917 Some redo log diagnostics is always reported as 0
The InnoDB monitor counter log_sys.n_log_ios was almost removed in commit 685d958e38b825ad9829be311f26729cccf37c46 (MDEV-14425). This counter was rather meaningless already since commit 30ea63b7d2077883713e63cbf4e661ba0345bf68 introduced a redo log group commit mechanism, and on the persistent memory interface there are no file system calls that could be counted. The only case when log_sys.n_log_ios was updated is when the log file was being read during crash recovery. Some related output in log_print() as well as the information_schema.innodb_metrics counter log_num_log_io are best removed.
Diffstat (limited to 'mysql-test/suite/innodb/r/monitor.result')
-rw-r--r--mysql-test/suite/innodb/r/monitor.result1
1 files changed, 0 insertions, 1 deletions
diff --git a/mysql-test/suite/innodb/r/monitor.result b/mysql-test/suite/innodb/r/monitor.result
index 0424ea51238..ce10aceb51b 100644
--- a/mysql-test/suite/innodb/r/monitor.result
+++ b/mysql-test/suite/innodb/r/monitor.result
@@ -146,7 +146,6 @@ log_lsn_current disabled
log_lsn_checkpoint_age disabled
log_lsn_buf_pool_oldest disabled
log_max_modified_age_async disabled
-log_num_log_io disabled
log_waits disabled
log_write_requests disabled
log_writes disabled