On Sun, Sep 14, 2008 at 6:50 AM, Arjen Lentz <[EMAIL PROTECTED]> wrote: > Hi Stu, Mats, > > On 13/09/2008, at 7:21 PM, Stewart Smith wrote: >> >> On Wed, Aug 20, 2008 at 05:51:43PM +0200, Mats Kindahl wrote: >>> >>> Some open issues are: >>> * Timestamps are currently down to nanosecond precision, but I question >>> if this is needed. It requires 8 bytes, which is almost half of the >>> header, so if we can reduce this for the common scenarios and maybe >>> have a timestamp where it is necessary, I think that would be a good >>> thing. >> >> offset? (periodicly have "set base timestamp" event). protobufs also >> have compressed integer. > > I don't care that much for timestamp. What one usually wants/needs is a > serial within each unique server-id (or within each file of each server-id); > I believe one of the Google patches does something like this?
This is in a future patch. We have implemented global transactions IDs (http://code.google.com/p/google-mysql-tools/wiki/GlobalTransactionIds) and shared the changes with Mas & Lars. We will publish the patch soon. Hopefully we will have per-event checksums in that patch too. > > >>> * Do we need to support encryption/compression of the individual events? >> >> We could do something with just reset encryption/compression scheme >> every so often and keep index (or, if using compression/encryption, just >> have smaller binlog files as you may have to seek through them). >> >> The trickier thing is cache management of compressed/uncompressed (and >> enc/dec) parts of the binlog :) > > > For storage... > - is encryption really necessary for Drizzle-style uses? > - compression... could be interesting, to reduce disk I/O. > Not too fussed about having to scan from start of a log file to decode, or > at least in large chunks. > > For transmission (to slaves), let's let stunnel deal with compression and > encryption. > Or did you want the server to just toss a complete compressed event at a > slave, with uncompressed header? Dunno if that's worth it. > The header needs to contain plenty of info (databases, tables, some other > foo) which could be subject to filtering on server-side at some point. > > > Cheers, > Arjen. > -- > Arjen Lentz, Founder @ Open Query > Training and Expertise for MySQL in Australia and New Zealand > http://openquery.com.au/training/ (ph. +61-7-3103 0809) > > > _______________________________________________ > Mailing list: https://launchpad.net/~drizzle-discuss > Post to : [email protected] > Unsubscribe : https://launchpad.net/~drizzle-discuss > More help : https://help.launchpad.net/ListHelp > -- Mark Callaghan [EMAIL PROTECTED] _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
