Cached data in phpMyAdmin

Klemen Stirn

• April 16, 2024 16:22

Hi,

The issue I am having is the data displayed in phpMyAdmin seems to be cached.

For example:

1. I list tables ("Structure" tab when viewing a database)
2. I select all tables having overhead
3. I optimize selected tables
4. when I list the tables again, they all still show having the same overhead

Second example:

1. I open a table and go to the "Operations" tab
2. I check AUTO_INCREMENT and it says 999
3. I manually add a new row to the database, it is inserted with ID 999
4. I check the AUTO_INCREMENT again, and it still says 999 instead of 1000

If I ANALYZE the table after making changes, the display in phpMyAdmin is correct in both examples above.

So, the phpMyAdmin display data is obviously cached somewhere, but where? How do I turn this off?

Cpanel 118.0.4
MySQL  8.0.36
cpsrvd 11.118.0.4
Database client version: libmysql - mysqlnd 8.1.27
PHP extension: mysqli Documentation curl Documentation mbstring Documentation
PHP version: 8.1.27
phpMyAdmin 5.2.1

Thank you,

Klemen

• 

  cPRex Jurassic Moderator

  • April 17, 2024 16:16

  Hey there!  This is a known issue we are working on as part of case CPANEL-43867.  I don't have any updates to share at this time since it is a recent case, but our team is aware of the issue.  I've added the details here to this case so if I hear any updates on my end I'll be sure to share them!

  0
• 

  Klemen Stirn

  • April 17, 2024 16:19

  Thank you for the update, cPRex!

  0
• 

  cPRex Jurassic Moderator

  • April 17, 2024 16:24

  Sure thing!

  0
• 

  cPRex Jurassic Moderator

  • April 25, 2024 16:41

  Update - it seems this has been an issue every since MySQL 8.0 was released, but very few people have noticed it in action.  PHPMyAdmin is aware and there is an open case with them here:

  https://github.com/phpmyadmin/phpmyadmin/issues/16378

  but at this point it'll be up to PHPMyAdmin to get this resolved.

  0
• 

  Klemen Stirn

  • April 25, 2024 16:56

  Cool, thanks for the info.

  Per the GitHub issue, I fixed it for myself with:

  SET GLOBAL information_schema_stats_expiry = 0;

  0
• 

  cPRex Jurassic Moderator

  • April 25, 2024 17:52

  Nice - I'm glad that worked!

  0

Please sign in to leave a comment.