+1

It could stay in the source tree but be disabled from a default build
(by flipping the setting in plugin.ini)

henrik

On Sat, Feb 18, 2012 at 4:24 PM, pcrews <[email protected]> wrote:
> On 02/18/2012 07:13 AM, David Shrewsbury wrote:
>>
>> Hi,
>>
>> On Feb 17, 2012, at 8:41 PM, Daniel Nichter wrote:
>>
>> <snip>
>>
>>> The big challenge in that list is slave which currently reads a config
>>> file.  It should be possible to start Drizzle with slave enabled, but no
>>> config, and then config and connect to the master dynamically.  After all,
>>> MySQL can dynamically re-connect to or change the master.  I'm not sure if
>>> the slave code is amenable to this requirement, but it must be made amenable
>>> else replication will suffer a serious blow to usability.
>>
>>
>> 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...
>>
>> 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.
>>
>> filtered_replicator - Should not be enabled by default. No
>> sense adding it unless you are replicating events AND
>> want to filter them.
>>
>> transaction_log - Should not be enabled by default. This is
>> the file-based transaction log (not used by the slave) and
>> is rather buggy, IMO. I almost feel like we should remove it
>> from the tree...
>
>
> I'd be in favor of removing the transaction_log if nobody objects.  I don't
> think it's bad code, but we see significant gains from using the
> innodb-based log / I'm not aware of anything that relies on this and suspect
> if anything does, that it could be adapted to use the bad-ass innodb rpl log
> : )
>
> Plus it is nice to trim out code / tests that aren't used but cause
> overhead.
>
> -Patrick
>>
>>
>> -Dave
>>
>> _______________________________________________
>> 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



-- 
[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

Reply via email to