Alex, 616e647265747469 andretti 616e6472e9737069 andr.spi
there is a character e9 in your string. It is not an ordinary character and can cause an error in the sorting order between InnoDB-.41 and InnoDB-.49. -----Original Message----- From: BAUMEISTER Alexandre <[EMAIL PROTECTED]> To: Heikki Tuuri <[EMAIL PROTECTED]> Cc: Michael Widenius <[EMAIL PROTECTED]>; [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: Tuesday, March 19, 2002 3:27 PM Subject: Re[2]: InnoDB: Assertion failure in thread 10 in file btr0btr.c line 574 >Heikki, > >HT> since you are French, I assume you have accent characters in the strings you >HT> have stored into your database. > >HT> The ordering of accent characters changed in 3.23.44! > > No accents. > > InnoDB tables on this server are mainly used for statistics, > counters etc ... > >HT> You must dump and reimport your tables to 3.23.49 so that the index trees >HT> are sorted in the right order. > > Since the crash we re-created everything so ... :) > > But I have still something strange with this server. > > I have two tables with the same create : > >create table popup( > campagne int(11) unsigned not null, > log char(20) not null, > cpt int(11), > unique(campagne,log), > index(log) >)type=InnoDB; > > and create table popup2 ... (same create). > > Table popup is not empty and is selected/updated from web pages > (counting popup screened). > > I'm inserting some data in table popup2 : > >mysql> insert into popup2 select '9',p.log,'1' from compte.portefeuilles p, compte.contenus_portefeuilles c where c.idport=p.idport and c.symbole='1rPEAD'; >Query OK, 41495 rows affected (27.06 sec) >Records: 52454 Duplicates: 10959 Warnings: 0 > > And then trying to insert into table popup all what is in table > popup2 : > >mysql> insert into popup select * from popup2; >ERROR 1213: Deadlock found when trying to get lock; Try restarting transaction >mysql> replace into popup select * from popup2; >ERROR 1213: Deadlock found when trying to get lock; Try restarting transaction > > I don't see why this deadlock ... MySQL binlogging requires that INSERT INTO ... SELECT ... sets shared locks on the SELECT table. To avoid the shared locks, use SELECT INTO OUTFILE and LOAD DATA INFILE. > Regards, > Alex. Regards, Heikki Innobase Oy --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
