On Tue, 12 Mar 2002, Sasha Pachev wrote:
> On Tuesday 12 March 2002 10:54 am, [EMAIL PROTECTED] wrote:
> > I created a ~5GB table full of large (TINY|BIG)TEXT fields in it. This is a
> fresh build and there has been no activity except for the following:
> > 1) Record inserts from flat file parsing.
> > 2) OPTIMIZE TABLE wich died in batch & caused me to try and run the REPAIR.
>
> Try our 3.23.49a binary. If it does not fix the problem, we would like to
> investigate the bug. Due to the large size of the table, if it does not
> compress well, or if you cannot reproduce the problem on a smaller table, or
> write a script that will create the table on which the problem can be
> reproduced, we will need to log in to your system and try it there.
The upgrade worked just fine.
I must say that your team has EXCELLENT reponse time & the solution given
was dead on target.
Thank you for quality support of an affordable product that is also of
high-quality.
rafe
>
> --
> MySQL Development Team
> For technical support contracts, visit https://order.mysql.com/
> __ ___ ___ ____ __
> / |/ /_ __/ __/ __ \/ / Sasha Pachev <[EMAIL PROTECTED]>
> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/
> /_/ /_/\_, /___/\___\_\___/ Provo, Utah, USA
> <___/
>
---------------------------------------------------------------------
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
