On Sat, Feb 18, 2012 at 2:13 PM, David Shrewsbury <[email protected]> wrote: > So the idea was that plugins would only be enabled based > on what the user needed. I don't think we ever intended to > match MySQL functionality straight out of the box. Leaner > and meaner and only what you need and whatnot...
You are both right. Currently many plugins are built so that they will not be loaded by default, only if you add --add-plugin. This is probably what most here think when someone says "by default". This is not intended to change. Otoh our deb and rpm packages package each plugin separately. They take the approach that if you installed the plugin, you want to use it. Therefore the packages will install a file in conf.d/ that does --add-plugin. Currently many plugins make the server abort on startup (due to missing configuration / bad default configuration). Daniel's work is to fix this problem. > That said, the slave plugin cannot be turned on by default > since there are no mechanisms to dynamically add masters > or alter how it works other than through the slave config file. > There were plans to add more to it in the future to re-enable > some of the dynamic config features. But obviously we are not > quite there. What Daniel said: We have to make it work. In fact, it is recommended (in MySQL world) not to configure replication from the config file but always do it dynamically after server restart. (The rationale is basically you don't want the server to start replicating from some random master just because a restart happened.) henrik -- [email protected] +358-40-8211286 skype: henrik.ingo irc: hingo www.openlife.cc My LinkedIn profile: http://www.linkedin.com/profile/view?id=9522559 _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
