Community provides HA patches that weren't yet merged into the official tree and probably wont make it before mysql 6. Possibility to patch with http://code.google.com/p/google-mysql-tools/wiki/Mysql5Patches http://www.percona.com/percona-lab.html (i.e. via a new useflag so that less adventurous people arent affected) would help a lot. Patches apply to both 5.0 and 5.1. Reproducible: Always
Queued for dev-db/mysql-5.0.70-r1.
adding a link to have a referebce to all major patchsets http://ourdelta.org/patches
(In reply to comment #1) > Queued for dev-db/mysql-5.0.70-r1. Did this occur? I recently emerged 5.0.70-r1, but I don't see that it has the mentioned patches (like the smpfix, etc). Michael
-r1 ended up being another security fix. I haven't changed the whiteboard because I got complaints about bugspam. Busy waiting for upstream input on a serious bug I found on 5.0.72.
This would be an incredibly useful feature but isn't it necessary to do this with dev-db/mysql-community rather than dev-db/mysql? I believe the the major patches are all against community edition. I think the best solution would just be to incorporate the Ourdelta patches since they already have an open release process for merging all of the patches into a release.
paul: The patches should apply equally to both of them, and I do intend to have it in both.
Any update on when this will be merged? I urgently need to run some diagnostics on indexes and mysql-proxy doesn't cut it. I'm wary of putting an ebuild of my own creation into production...
*** Bug 244938 has been marked as a duplicate of this bug. ***
1. The Percona 5.0.75 patches don't apply against 5.0.76. There's LOTS of rejects in them. They do however apply on top of Gentoo-patched community 5.0.75 edition. 2. OurDelta seems to have a fully patched source tarball of 5.0.67, but no individual patches, nor anything newer than 5.0.67. So for the moment, I'm going to apply the Percona patches on community 5.0.75 (just running testcases on it now). I'd LOVE it if somebody could find me respins of the patches that applied on top of 5.0.76.
5.0.75-r1 is in the tree now.