Hi Thomas,
I don't see at all why your debian-sys-maint would not have access to
information_schema, to me this is an issue in YOUR SYSTEM not in the
package. It's been a while that the package is running on many of our
servers running Lenny without an issue, why would it suddenly break like
this? This makes no sense at all to me. Please check your system, maybe
try to reinstall it from scratch, and come back to write in this bug
entry. I'll leave it open for few days until I have a reply from you again.
after further investigation it seems that this error occurred the first
time after the upgrade from mysql version 5.1.37 to 5.1.39. The
changelog does not give any hint to me, but I did not read very deep
into it.
What I found in the mysql documentation is:
Tables in the INFORMATION_SCHEMA database are an exception. They can be
accessed without being locked explicitly even while a session holds
table locks obtained with LOCK TABLES.
Maybe there was something changed in 5.1.38 or 5.1.39 regarding the
locking of this specific database?
Inside the automysqlbackup script, the option "--opt" is always used for
mysqldump calls; a "--skip-opt" for information_schema would not lock
the table.
Regards,
Michael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
