[debian-mysql] Bug#727193: still unresolved?
Daniel Pocock
daniel at pocock.pro
Tue Feb 10 08:37:28 UTC 2015
What is the status of this bug?
The upstream discussion in bug 68376 talks about the technicalities of
turning this on and off but it doesn't really give any insight into what
people should do in practice
For example,
- Why does it skip that table and no other table?
- Would it be better to dump the table like all other tables and just
take care not to load it again unless appropriate?
- There must be some reason why they exclude this table by default, what
are the factors people should think about when deciding if they do want
or need to include that table in their dump?
More people are going to encounter this when upgrading to jessie if they
haven't upgraded their MySQL for a long time.
More information about the pkg-mysql-maint
mailing list