Package: mysql-server-5.0 Version: 5.0.32-7etch5 Severity: normal Tags: patch
There has been a longstanding problem with MySQL replication relaylogs becoming corrupted for unknown (probably network error related) reasons. Several mysql bugs are open on the issue, including: http://bugs.mysql.com/bug.php?id=26489 which has been open for just over a year. In this ticket, a good fix was finally found and committed upstream for both MySQL-5.0 and MySQL-5.1. Commit message containing the patch for 5.0 is here: http://lists.mysql.com/commits/41342 I don't believe this problem affects normal single-server mysql installations, which is why I rated it as "normal", but for people who are doing wide-area replication with large amounts of traffic, this is a very serious problem that we've been impatiently waiting for MySQL to fix for a while now, and a backport into etch would be much appreciated. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-5-amd64 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
