Replication Bug on 4.0.18 with HEAP Tables
Replication Bug on 4.0.18 with HEAP Tables
am 07.08.2004 12:50:03 von gc
--_=_=_=IMA.BOUNDARY.I22ORF138764=_=_=_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Hi!
we use HEAP-Tables on our server for temporary data and so we create them with PHP, Insert Data INTO and do then DROP the Table in the same script.
on the slave it seams, that the DROP-Command was before the CREATE.
here is the error-log:
ERROR: 1146 Table 'WEB_BZ.OL_Kat_1091859321' doesn't exist
040807 12:05:10 Slave: Error 'Table 'WEB_BZ.OL_Kat_1091859321' doesn't exist' on query 'DELETE FROM `WEB_BZ`.`OL_Kat_1091859321`'. Default database: 'WEB_BZ', Error_code: 1146
040807 12:05:10 Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE$
ERROR: 1050 Table 'OL_Kat_1091859321' already exists
040807 12:06:16 Slave: Error 'Table 'OL_Kat_1091859321' already exists' on query 'CREATE TABLE OL_Kat_1091859321 TYPE=HEAP
SELECT AID FROM ADRESSEN_ADRESSKATEGORIEN INNER JOIN ADRESSKATEGORIEN ON ADRESSEN_ADRESSKATEGORIEN.KID=ADRESS$
WHERE (ADRESSEN_ADRESSKATEGORIEN.KID=2 OR ADRESSEN_ADRESSKATEGORIEN.KID=63) AND KStatus>=2
GROUP BY AID
HAVING COUNT(*)=2'. Default database: 'WEB_BZ', Error_code: 1050
040807 12:06:16 Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE$
ERROR: 1146 Table 'WEB_BZ.OL_Kat_1091863020' doesn't exist
040807 12:07:41 Slave: Error 'Table 'WEB_BZ.OL_Kat_1091863020' doesn't exist' on query 'DELETE FROM `WEB_BZ`.`OL_Kat_1091863$
040807 12:07:41 Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE$
ERROR: 1050 Table 'OL_Kat_1091863020' already exists
040807 12:09:13 Slave: Error 'Table 'OL_Kat_1091863020' already exists' on query 'CREATE TABLE OL_Kat_1091863020 TYPE=HEAP
SELECT AID FROM ADRESSEN_ADRESSKATEGORIEN INNER JOIN ADRESSKATEGORIEN ON ADRESSEN_ADRESSKATEGORIEN.KID=ADRESS$
WHERE (ADRESSEN_ADRESSKATEGORIEN.KID=24 OR ADRESSEN_ADRESSKATEGORIEN.KID=75) AND KStatus>=2
GROUP BY AID
HAVING COUNT(*)=2'. Default database: 'WEB_BZ', Error_code: 1050
040807 12:09:13 Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE$
ERROR: 1146 Table 'WEB_BZ.OL_Kat_1091864175' doesn't exist
040807 12:09:34 Slave: Error 'Table 'WEB_BZ.OL_Kat_1091864175' doesn't exist' on query 'DELETE FROM `WEB_BZ`.`OL_Kat_1091864$
040807 12:09:34 Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE$
ERROR: 1050 Table 'OL_Kat_1091864175' already exists
040807 12:10:04 Slave: Error 'Table 'OL_Kat_1091864175' already exists' on query 'CREATE TABLE OL_Kat_1091864175 TYPE=HEAP
SELECT AID FROM ADRESSEN_ADRESSKATEGORIEN INNER JOIN ADRESSKATEGORIEN ON ADRESSEN_ADRESSKATEGORIEN.KID=ADRESS$
WHERE (ADRESSEN_ADRESSKATEGORIEN.KID=23 OR ADRESSEN_ADRESSKATEGORIEN.KID=132) AND KStatus>=2
GROUP BY AID
HAVING COUNT(*)=2'. Default database: 'WEB_BZ', Error_code: 1050
the SHOW SLAVE STATUS says:
db3.edev.at repl 3306 60 alhambra-bin.001 43146529 bohnanza-relay-bin.001 28632351 alhambra-bin.001 Yes No 1146 Error 'Table 'WEB_BZ.OL_Kat_1091864184' doesn't ex... 0 42964863 28814017
System is:
Master and Slave are both with OpenBSD 3.5 Current
Master is P4 / 2.4 with 1GB RAM, Slave is Duron 1000 with 1GB
mysql 4.0.18 on OpenBSD3.5 build from the ports-tree.
OpenBSD bohnanza.edev.at 3.5 GENERIC#0 i386
Other information is attached
is it a bug or can you give us a hint ?
christian groesswang
------------------------------------------------------
P.I.C.S. GmbH.
EDV & Unternehmensberatung
Landsturmstrasse 18
A-5020 Salzburg
Tel: 0662 / 455 467
Fax: 0662 / 455 468
Email: gc@pics.co.at
------------------------------------------------------
--_=_=_=IMA.BOUNDARY.I22ORF138764=_=_=_
Content-Type: text/plain; charset=us-ascii
--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org
--_=_=_=IMA.BOUNDARY.I22ORF138764=_=_=_--
Re: Replication Bug on 4.0.18 with HEAP Tables
am 10.08.2004 14:57:34 von Sergei Golubchik
Hi!
On Aug 07, Ing. Christian Groesswang wrote:
> Hi!
>
> we use HEAP-Tables on our server for temporary data and so we create
> them with PHP, Insert Data INTO and do then DROP the Table in the same
> script.
Please check whether
http://bugs.mysql.com/bug.php?id=4971
is the same bug or not.
If not - could you report you bug on http://bugs.mysql.com ?
Regards,
Sergei
--
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Sergei Golubchik
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Senior Software Developer
/_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany
<___/ www.mysql.com
--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org
Bug in 4.0.20: CONCAT function and "double" type
am 17.08.2004 16:49:30 von Mikhail Entaltsev
Hi,
It seems like it is a bug in MySQL version 4.0.20-standard-log.
Comparison between string and concat function returns wrong result.
Look at short example:
CREATE TABLE `Tmp` (
`A` char(4) NOT NULL default '',
`B` double default NULL,
`C` date default NULL,
`D` tinyint(4) default NULL
) TYPE=MyISAM;
insert into Tmp (A,B,C,D) values ('AAAA',105,'2003-03-01',1);
select * from Tmp where concat(A,C,B,D) = 'AAAA2003-03-011051';
# 0 records - BUG!!!
It returns 0 records and it is wrong!
But if you will change fields order in the concat function it will work fine
(it returns 1 record):
select * from Tmp where concat(A,B,C,D) = 'AAAA1052003-03-011';
# FALSE as comparison result - BUG!!!
select concat(A,C,B,D),'AAAA2003-03-011051',(concat(A,C,B,D) =
'AAAA2003-03-011051') from Tmp;
# TRUE as comparison result
select concat(A,B,C,D),'AAAA1052003-03-011',(concat(A,B,C,D) =
'AAAA1052003-03-011') from Tmp;
drop table Tmp;
But if you change type of the 'B' field from double to int everything is
working fine:
CREATE TABLE `Tmp1` (
`A` char(4) NOT NULL default '',
`B` int default NULL,
`C` date default NULL,
`D` tinyint(4) default NULL
) TYPE=MyISAM;
insert into Tmp1 (A,B,C,D) values ('AAAA',105,'2003-03-01',1);
select * from Tmp1 where concat(A,C,B,D) = 'AAAA2003-03-011051';
select * from Tmp1 where concat(A,B,C,D) = 'AAAA1052003-03-011';
select concat(A,C,B,D),'AAAA2003-03-011051',(concat(A,C,B,D) =
'AAAA2003-03-011051') from Tmp1;
select concat(A,B,C,D),'AAAA1052003-03-011',(concat(A,B,C,D) =
'AAAA1052003-03-011') from Tmp1;
drop table Tmp1;
Best regards,
Mikhail.
--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org
Re: Bug in 4.0.20: CONCAT function and "double" type
am 13.09.2004 12:28:19 von Mikhail Entaltsev
Hi,
I have sent that email ~1 month ago but didn't see anything related to it on
the mail-list.
Just would like to be sure that someone from MySQL AB get it.
Thanks in advance,
Mikhail.
----- Original Message -----
From: "Mikhail Entaltsev"
To:
Sent: Tuesday, August 17, 2004 4:49 PM
Subject: Bug in 4.0.20: CONCAT function and 'double' type
> Hi,
>
> It seems like it is a bug in MySQL version 4.0.20-standard-log.
> Comparison between string and concat function returns wrong result.
> Look at short example:
>
> CREATE TABLE `Tmp` (
> `A` char(4) NOT NULL default '',
> `B` double default NULL,
> `C` date default NULL,
> `D` tinyint(4) default NULL
> ) TYPE=MyISAM;
>
> insert into Tmp (A,B,C,D) values ('AAAA',105,'2003-03-01',1);
>
> select * from Tmp where concat(A,C,B,D) = 'AAAA2003-03-011051';
> # 0 records - BUG!!!
>
> It returns 0 records and it is wrong!
> But if you will change fields order in the concat function it will work
fine
> (it returns 1 record):
>
> select * from Tmp where concat(A,B,C,D) = 'AAAA1052003-03-011';
>
> # FALSE as comparison result - BUG!!!
> select concat(A,C,B,D),'AAAA2003-03-011051',(concat(A,C,B,D) =
> 'AAAA2003-03-011051') from Tmp;
> # TRUE as comparison result
> select concat(A,B,C,D),'AAAA1052003-03-011',(concat(A,B,C,D) =
> 'AAAA1052003-03-011') from Tmp;
> drop table Tmp;
>
> But if you change type of the 'B' field from double to int everything is
> working fine:
>
> CREATE TABLE `Tmp1` (
> `A` char(4) NOT NULL default '',
> `B` int default NULL,
> `C` date default NULL,
> `D` tinyint(4) default NULL
> ) TYPE=MyISAM;
> insert into Tmp1 (A,B,C,D) values ('AAAA',105,'2003-03-01',1);
> select * from Tmp1 where concat(A,C,B,D) = 'AAAA2003-03-011051';
> select * from Tmp1 where concat(A,B,C,D) = 'AAAA1052003-03-011';
> select concat(A,C,B,D),'AAAA2003-03-011051',(concat(A,C,B,D) =
> 'AAAA2003-03-011051') from Tmp1;
> select concat(A,B,C,D),'AAAA1052003-03-011',(concat(A,B,C,D) =
> 'AAAA1052003-03-011') from Tmp1;
> drop table Tmp1;
>
>
> Best regards,
> Mikhail.
>
>
> --
> MySQL Bugs Mailing List
> For list archives: http://lists.mysql.com/bugs
> To unsubscribe: http://lists.mysql.com/bugs?unsub=mentaltsev@cmtkg.com
>
>
--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org
Re: Bug in 4.0.20: CONCAT function and "double" type
am 13.09.2004 16:30:19 von Sergei Golubchik
Hi!
On Aug 17, Mikhail Entaltsev wrote:
> Hi,
>
> It seems like it is a bug in MySQL version 4.0.20-standard-log.
> Comparison between string and concat function returns wrong result.
> Look at short example:
....
It was submitted as http://bugs.mysql.com/bug.php?id=5540
use this page to track the progress of your report.
Regards,
Sergei
--
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Sergei Golubchik
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Senior Software Developer
/_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany
<___/ www.mysql.com
--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org