Most likely it's the 4GB OS limitation... My suggestion is to create a new table using mysql's built in raid option... span the table over multiple files to allow of much larger table growth...
migrate all the rows over to the new spanned table.. On Thu, 4 Sep 2003, Keith C. Ivey wrote: > On 4 Sep 2003 at 10:53, Keith Bussey wrote: > > > Your suggestion seemed to wipe out my rows ! (s'ok I got a backup ;p) > > Yikes! Are you running into any file system limits? Have you dealt > with files larger than 4 GB on that server before with no problems? > If not, you may have run into a MySQL bug of some sort. > > An alternative way to get the table to have 5-byte pointers would be > to create the new table (same CREATE TABLE query as for the old > structure, except add "MAX_ROWS=700000 AVG_ROW_LENGTH=20000" to the > end) and then copy all the records into it: > > INSERT INTO email_body_NEW SELECT * FROM email_body; > > Actually, the exact figures for MAX_ROWS and AVG_ROW_LENGTH shouldn't > matter, as long as their product is between 2**32 and 2**40 - 1. > > -- > Keith C. Ivey <[EMAIL PROTECTED]> > Tobacco Documents Online > http://tobaccodocuments.org > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
