Hi!
On Oct 06, Christopher L. Everett wrote:
> I have an application where I create a faily large table (835MB) with a
> fulltext index. One of our development workstations and our production
> server will run the script to load the table, but afterwards we have a
> pervasive corruption, with out
Hi!
On Oct 06, Christopher L. Everett wrote:
> I've also found a problem with "myisamchk --sort-keys":
I recently fixed one bug in myisamchk --sort-keys where fulltext indexes
are present. Try 4.1.7 release.
Regards,
Sergei
--
__ ___ ___ __
/ |/ /_ __/ __/ __ \/ / Sergei Go
Ed Lazor wrote:
-Original Message-
From: Christopher L. Everett [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 06, 2004 1:47 AM
To: Mysql List
Subject: Repeated corruption with MySQL 4.1.x using FULLTEXT indexes
I have an application where I create a faily large table (835MB) with a
ful
> -Original Message-
> From: Christopher L. Everett [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 06, 2004 1:47 AM
> To: Mysql List
> Subject: Repeated corruption with MySQL 4.1.x using FULLTEXT indexes
>
> I have an application where I create a faily large table (835MB) with a
> fu
I've also found a problem with "myisamchk --sort-keys":
christopher:/var/lib/mysql/dmoz# myisamchk -rq xurls
- check record delete-chain
- recovering (with sort) MyISAM-table 'xurls'
Data records: 1981904
- Fixing index 1
- Fixing index 2
- Fixing index 3
Data records: 4332227
christopher:/var/lib/
