Hi Daniel!

Great points, and certainly something that many have asked for.  I went
ahead and added a Blueprint task for this so that developers can target
code and branches towards this:

https://blueprints.launchpad.net/drizzle/+spec/runtime-configuration-changes

Question for all:

Should we target this for the Cirrus milestone?

Cheers,

Jay

Daniel Gary wrote:
> I ran across a pet peeve yesterday evening
> 
> namely --replicate-do-db=blah, well replicate-do-db=blah in my case
> since it was in my.cnf
> (yes, I have a database named blah)
> 
> pet peeve being, I have to bring my server down to change whats being
> replicated,
> which got me thinking of all the things that I can and can't change
> during runtime
> 
> so I'll even ask nicely,
> whoever is doing the new replication code, can we please please please
> make slaves be able to change what they replicate on the fly?
> I'm envisioning something similar to the whole stop slave; change
> master; start slave; process
> 
> I mean really, the only thing I don't think we should be able to change
> during runtime is maybe datadir, but even then I can see times when
> that'd be very useful
> and while I can see it would be seriously non-trivial, I would like to
> be able to change buffer sizes on the fly
> 
> just food for thought
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~drizzle-discuss
> Post to     : [email protected]
> Unsubscribe : https://launchpad.net/~drizzle-discuss
> More help   : https://help.launchpad.net/ListHelp

_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help   : https://help.launchpad.net/ListHelp

Reply via email to