[debian-mysql] Bug#727193: Bug#727193: still unresolved?

Norvald H. Ryeng norvald.ryeng at oracle.com
Tue Feb 10 12:46:02 UTC 2015


On Tue, 10 Feb 2015 09:37:28 +0100, Daniel Pocock <daniel at pocock.pro>  
wrote:

> What is the status of this bug?

The status is "forwarded", which means it's been forwarded to upstream.  
Upstream has closed it as not a bug. I guess we should close it in Debian  
too.

>
> 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?

Probably because it has traditionally done so.

The first upstream bug report I can find about the issue is  
http://bugs.mysql.com/bug.php?id=16853. That ended by implementing the  
--events option (in 5.1.8 in 2006).

Then there was a bug report that it silently skipped the events table:  
http://bugs.mysql.com/bug.php?id=55587. That bug was fixed (in 5.1.68 and  
5.5.30) by issuing the warning that this bug report is complaining about.  
In 5.6 and 5.7, the default behavior is to include the table.

> - Would it be better to dump the table like all other tables and just
> take care not to load it again unless appropriate?

5.6 and 5.7 already does this. I don't think that will be changed in 5.5  
now. 5.1 is EOL and doesn't receive any more updates.

> - 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?

I don't know why it was skipped to begin with. In MySQL 5.6 and later, it  
is included by default. You'll have to use an option to exclude it.

The option is documented in  
http://dev.mysql.com/doc/refman/5.1/en/mysqldump.html#option_mysqldump_events.  
You'll have to evaluate your use case to decide if it's needed or not.

> More people are going to encounter this when upgrading to jessie if they
> haven't upgraded their MySQL for a long time.

The same behavior is there in wheezy, so it shouldn't come as a surprise  
in jessie.

Regards,

Norvald H. Ryeng



More information about the pkg-mysql-maint mailing list