AMD64 and thread stack size

2005-01-28 Thread Frank Denis \(Jedi/Sector One\)
It looks like the default thread stack is not large enough for MySQL 4.1 on Linux running on AMD64. With NPTL, the database quickly crashed after a few hours of heavy load (segv). Without NTPL, I believed it wasn't the case. But after one week mysqld process were stuck in a strange

2 gigs limits on MyISAM indexes?

2005-01-28 Thread Frank Denis \(Jedi/Sector One\)
Is there a limit on the size of .MYI files? I have a database that worked flawlessly until today. I can't restart it, it immediately freezes. I noticed that the .MYI file of a table has reached exactly 2 gigs. May it be related? Is there anything to do in order to recover the data

Re: 2 gigs limits on MyISAM indexes?

2005-01-28 Thread Frank Denis \(Jedi/Sector One\)
On Fri, Jan 28, 2005 at 04:00:24PM +, Mat wrote: What Operating System are you running this on? Linux 2.6, 64 bits. MySQL 4.1.9. Also, is there anything in the errorlog? Nothing, but as soon as I restart the server, it enters a strange state where all slots are full with

Rows_sent vs Rows_examined

2005-01-12 Thread Frank Denis \(Jedi/Sector One\)
Just wondering... I have this simple join: SELECT b.id_commentaire AS id_commentaire, id_skynaute, id_article, created_on, read, expediteur, email, text FROM comment_base AS b LEFT JOIN comment_content AS c USING (id_commentaire) WHERE id_skynaute = 4671022 AND id_article = 58366086;

InnoDB status: why do I see MyISAM requests?

2004-12-12 Thread Frank Denis \(Jedi/Sector One\)
Just curious... While running SHOW INNODB STATUS, the list of transactions for each sessions part shows queries that are only related to MyISAM tables. Is it the expected behavior? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:

Re: problems with php 4.3.9 / mysql 4.1.7

2004-12-08 Thread Frank Denis \(Jedi/Sector One\)
On Wed, Dec 08, 2004 at 11:25:55AM +0100, Bogdan TARU wrote: Everything went ok, up until the point when I tried linking PHP-4.3.9 against MySQL-4.1.7. After starting the new Apache/PHP (ldd httpd shows '/usr/local/mysql-4.1.7/lib/mysql/libmysqlclient.so.14'), I get a whole lot of

Question about auto-increment columns

2003-02-19 Thread Jedi/Sector One
/Sector One) [EMAIL PROTECTED] -*\ __ \ '/a href=http://www.PureFTPd.Org/; Secure FTP Server /a\' / \/ a href=http://www.Jedi.Claranet.Fr/; Misc. free software /a \/ - Before posting, please check: http

Re: Question about auto-increment columns

2003-02-19 Thread Jedi/Sector One
://marc.theaimsgroup.com/?l=mysqlm=94495471802684w=2 Ok, except speculation on real life, there's no correct way to handle this. -- __ /*- Frank DENIS (Jedi/Sector One) [EMAIL PROTECTED] -*\ __ \ '/a href=http://www.PureFTPd.Org/; Secure FTP Server /a\' / \/ a href=http://www.Jedi.Claranet.Fr

Re: Question about auto-increment columns

2003-02-19 Thread Jedi/Sector One
On Wed, Feb 19, 2003 at 10:43:41AM +0059, Jedi/Sector One wrote: Ok, except speculation on real life, there's no correct way to handle this. Self-correction : it looks like MySQL returns ER_DUP_ENTRY when an overflow occurs, even with InnoDB tables. Great :) -- __ /*- Frank DENIS