Matthew, Wednesday, October 02, 2002, 5:29:38 PM, you wrote: MJF> My company runs a moderately large and loaded MySQL replication network MJF> across four Solaris machines. While upgrading from a fairly old 3.23.4x MJF> installation to 3.23.52 we've encountered a problem with replication and MJF> binlog rotation. MJF> One of the machines is simultaneously slave to one server and master to MJF> two others; on that machine, if a "RESET MASTER" or "PURGE MASTER LOGS" MJF> is executed while its slave thread is performing a query, mysqld MJF> reproducibly dies.
MJF> Looking in the mysql list archives, I see one other report of something MJF> similar, but no detailed bug reports or resolution. [skip] I also saw the similar bug report, but I couldn't repeat it. Could you test it with our binaries? -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Victoria Reznichenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net <___/ 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
