Hi!
>>>>> "Melvyn" == Melvyn Sopacua <[EMAIL PROTECTED]> writes: <cut> Melvyn> I don't get the checksum errors anymore - after I changed the table def. Melvyn> However - myisamchk is not doing a good job with the large keys (restored Melvyn> them by LOAD TABLE hardware FROM MASTER which produced the correct size), Melvyn> plus keys become corrupted when a replication packet is not received correctly, Melvyn> plus: mysql> SHOW VARIABLES LIKE '%ft%'; Melvyn> Empty set (0.07 sec) Can you create an example that shows that you how get a corrupted table when a replication packet fails ? This is something that should not be possible to happen. If failed packet doesn't have anything to do with a crashed table. On the other hand, you may got a crashed table on the slave and the replication stops because of this; This is however another issue. Melvyn> The myisamchck is certainly reproducable, as is the missing ft_ variables, Melvyn> resulting in no way to set ft_min_word_len. myisamchk in 4.0 supports the ft_min_word_len variable. If you change ft_min_word_len, you are probably better of with using REPAIR TABLE than myisamchk to repair a table. Melvyn> Should I re-report those bugs, so they are easier to process for you? Yes, if you can produce a full test case. Melvyn> Today I think I found something interesting: Melvyn> Some tables kept crashing, with incorrect keyfiles. Melvyn> Verifying the CREATE TABLE statement, there's was 1 correlation: Melvyn> The tables all had a second index on the primary key (for what reason? I don't Melvyn> know - legacy probably - I think the primary key, was dual-fielded at some Melvyn> point). I don't think this is the problem; There is no requirements inside MySQL to have the primary index as the first index. Melvyn> Combining that with the other table that kept crashing there seems to be a Melvyn> problem, Melvyn> with the situation, where one field is indexed more than one time. I would be really interested in having a test case that shows how to crash MySQL. Without a test case, I can't really give you any good advises of what could be the problem. Regards, Monty -- For technical support contracts, goto https://order.mysql.com/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Mr. Michael Widenius <[EMAIL PROTECTED]> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, CTO /_/ /_/\_, /___/\___\_\___/ Helsinki, Finland <___/ www.mysql.com --------------------------------------------------------------------- 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
