Re: unusable binlog when 2 connections use the same temporary table names - Peter Zaitsev - com.mysql.lists.bugs

3 messages in com.mysql.lists.bugsRe: unusable binlog when 2 connection...

From	Sent On	Attachments
Guilhem Bichot	20 Oct 2002 06:51
Peter Zaitsev	20 Oct 2002 09:46
Michael Widenius	21 Oct 2002 04:45

Subject:	Re: unusable binlog when 2 connections use the same temporary table names
From:	Peter Zaitsev (pet...@mysql.com)
Date:	10/20/2002 09:46:53 AM
List:	com.mysql.lists.bugs

On Sunday 20 October 2002 17:51, Guilhem Bichot wrote:

Description: This may be already known, but it seems to be a long-lasting bug. In 3.23.47 linux and few-days-old 4.1 linux, if 2 connections create temporary tables with the same name, the binlog gets unusable.

Sorry I I'm not sure about your example: You do not have tables as "temporary" below so it is obvious it shall not work - it just should fail upon second table creation.

Also I'm not sure what do you mean by "unusable binlog" does replication breaks for you or you're trying to dump the log to text format and see this text in it ?

Replication is known to work with temporary tables, in case you do not shut down slave while the it has temporary tables open, while you can't dump it to text file and use properly.

How-To-Repeat: In thread 1 do : create table test.t (a int); keep this thread open (keep the mysql client open) In thread 2 do : create table test.t (b char(1)); flush logs; And examine the binlog : it contains, in short : create table test.t (a int); create table test.t (b char(1)); Which will result in errors when piping the output of mysqlbinlog into mysql ("table t already exists") and make the binlog unusable (and recovery impossible).

Fix: ?

To request this thread, e-mail bugs...@lists.mysql.com To unsubscribe, e-mail <bugs...@lists.mysql.com>