Closed dabico closed 1 week ago
This is strange, and maybe I don't understand what MySQL is doing with these "background histogram updates", but it seems like it's pretty harmless, right? Wouldn't it retry the background updates later? Maybe there's a way for your database dump / import to (temporarily) disable these so that they don't run during your import, or to make them an explicit part of the import somehow instead?
Either way, I think this is probably firmly in the territory of "upstream behavior changes" not something caused by / that might be fixed by changes to the Docker images we package/maintain, and thus a more specific MySQL support forum might lead to more fruitful debugging :see_no_evil: :bow:
This is strange, and maybe I don't understand what MySQL is doing with these "background histogram updates", but it seems like it's pretty harmless, right?
I'm inclined to think that it has something to do with the dump itself. Looking at the SQL, all table INSERT
statements are preceded by a LOCK TABLES 'TABLE' WRITE
. Not sure if (and how) this affects the background histogram updates.
Either way, I think this is probably firmly in the territory of "upstream behavior changes"...
Yeah you're right, I only reported this here because I don't use MySQL on my local machine. Since I only use the DB with Docker, I thought I might ask here first. Either way, I will open an issue upstream. Thanks for the help!
Edit:
I've opened an issue upstream: https://bugs.mysql.com/bug.php?id=116145
Are there any updates on this?
Are there any updates on this?
Yes, please refer to the upstream report.
I recently upgraded the image to the latest major version and noticed some strange warnings when trying to import an existing SQL dump during initialisation. There does not appear to be anything wrong with the imported data, but the warnings indicate some type of locking issues during the import process.
Expected Behaviour (8.3.0)
Actual Behaviour (9.0.1)