Bug #112075 | innodb_cached_indexes.n_cached_pages reports crazy high numbers | ||
---|---|---|---|
Submitted: | 15 Aug 2023 15:09 | Modified: | 22 Mar 3:33 |
Reporter: | Jay Janssen | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | 8.0 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[15 Aug 2023 15:09]
Jay Janssen
[16 Aug 2023 11:58]
MySQL Verification Team
Hi Mr. Janssen, Thank you for your bug report. However, please do note that this is a forum for the bugs with a fully repeatable test cases that always lead to the bug showing up. This is not a forum for asking questions. Regarding your questions, InnoDB pages can be both cached and removed from the cache. What you see is the number of times pages have been cached, while removal from the cache is not counted. Not a bug.
[16 Aug 2023 14:51]
Jay Janssen
At least the documentation is not very clear https://dev.mysql.com/doc/refman/8.0/en/information-schema-innodb-cached-indexes-table.htm... says: ``` N_CACHED_PAGES The number of index pages cached in the InnoDB buffer pool. ``` It should read "The total number of index pages cached in the Innodb buffer pool since server startup for this specific index". As it reads currently, it makes it sound like that is the _current_ number of cached pages.
[16 Aug 2023 14:55]
MySQL Verification Team
Hi, The current explanation is very clear. It does NOT say that this is a CURRENT number of pages being cached.
[16 Aug 2023 17:09]
MySQL Verification Team
This is now a verified Documentation bug.
[22 Mar 3:33]
Philip Olson
Posted by developer: Thanks Jay for reporting this bug and offering a suggestion to improve the documentation, this is now fixed in the documentation source.
[22 Mar 11:14]
MySQL Verification Team
Thank you, Phillip.