Bug #48278 | InnoDB replication | ||
---|---|---|---|
Submitted: | 24 Oct 2009 9:48 | Modified: | 24 Oct 2009 21:07 |
Reporter: | boobalan m | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server: Backup | Severity: | S1 (Critical) |
Version: | 5.2 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | InnoDB replication |
[24 Oct 2009 9:48]
boobalan m
[24 Oct 2009 11:03]
Peter Laursen
If you are serious that you use a MySQL 5.2 server, I think that you should try 5.4.3 (or latest 6.0.x) instead. 5.2 was the name of what later became 6.0. 6.0 is now also not maintained (but this policy seems a little ambiguous though). New features introduced in 5.2/6.0 will be available in 5.4 as they approach production quality @MySQL people: please delete the 5.2 tree from FTP mirrors (like ftp://mirrors.dotsrc.org/mysql/Downloads/MySQL-5.2/ ) This tree has not been updated for 2½+ years. It is also confusing our users periodically. Some people seem to think that '5.2 is better than 5.1'. :-( Peter (not a MySQL person)
[24 Oct 2009 21:07]
MySQL Verification Team
Not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.mysql.com/how-to-report.php If you can provide more information, feel free to add it to this bug and change the status back to 'Open'. Thank you for your interest in MySQL.