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 of range index index pointer errors. Oddly, my development workstation doesn't have those problems.
My box and the ones having the problems have the following differences:
- my box runs ReiserFS, the problem boxes run XFS - my box has a nice SCSI HD subsystem, the problem boxes do IDE.
All three boxes run Linux 2.6.x kernels, and my workstation and production server share the same mobo. Come to think of it, I saw similar corruption issues under 2.4.x series kernels and MySQL v4.0.x, it just wasn't the show stopper it is now.
Also, on all three boxes, altering the table to drop an index and create a new one requires a "myisamchk -rq" run afterwards when a fulltext index either exists or gets added or dropped, which I'd also call a bug.
-- Christopher L. Everett
Chief Technology Officer www.medbanner.com MedBanner, Inc. www.physemp.com
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
