Re: [4.0.14] Small bug with OPTIMIZE/ANALYZE and FULLTEXT index
Sinisa Milivojevic <[email protected]>
| Newsgroups | gmane.comp.db.mysql.bugs |
|---|---|
| Message-ID | <[email protected]> |
Matt W writes: > Hi Sinisa! > > Thanks for replying, but... you can't see that this is a bug? :-) The > behavior is *NOT* consistent with *any* other version of MySQL I've > *ever* used OPTIMIZE/ANALYZE on with MyISAM tables. If it's not a bug, > then all the other versions must have the bug. :-) > > I thought it would a simple bug report. But now I have investigated > further to give more details about the problem. I hope you can see the > bug. ;-) The problem seems to be, as I discovered with myisamchk, that > the table is not remembering that it was analyzed when it has a FULLTEXT > index. > You have UPDATE'd a tuple with longer row. Then there is some work for OPTIMIZE. Regarding error message, this has been fixed , and will come in 4.0.15. -- Sincerely, -- For technical support contracts, go to https://order.mysql.com/?ref=msmi __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic <[email protected]> / /|_/ / // /\ \/ /_/ / /__ MySQL AB /_/ /_/\_, /___/\___\_\___/ Fulltime Developer and Support Coordinator <___/ www.mysql.com Larnaca, Cyprus -- MySQL Bugs Mailing List For list archives: http://lists.mysql.com/bugs To unsubscribe: http://lists.mysql.com/[email protected]