Comment 3 for bug 1736139
Revision history for this message
| Sergei Glushchenko (sergei.glushchenko) wrote | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Good point. I see couple of issues here:
1. there seems to be no good way to find out which zlib version is in use by server (except maybe parsing an mysql.err which is not always possible)
2. prepare (this error pops out only during prepare stage) can be done on different host with different environment, it means we need to save zlib version along with the backup and abort early if it doesn't match