On 8/14/08, Brian Aker <[EMAIL PROTECTED]> wrote: > > Hi! > > On Aug 14, 2008, at 5:27 AM, Baron Schwartz wrote: > > The problem I'm pointing towards is that currently the synchronization >> between the binlogs and InnoDB causes a lot of extra fsyncs for each >> commit. >> > > Unfortunately there is only a couple of solutions for a safe commit. > > 1) Let one engine lead the charge on sync (I like this). > 2) Store binlog in Innodb (Hmmm might work). > 3) Punt like we did in the past (I dislike this) > 4) ? > > Cheers, > -Brian
2) interesting idea. some things are appealing, others make me cringe. If we did this we should put the binlogs in a different ibdata file (even if the server isn't running innodb_file_per_table). Would PURGE MASTER LOGS automatically OPTIMIZE the table to get the storage back? Can there be more than one binary log file in this case? How could we apply binary logs to a server? (ie, for incremental backup purposes). Would there still be a mysqlbinlog tool? (it's sometimes nice to grep through the text of binary logs) What would a CHANGE MASTER statement look like? It'd be neat to extend the BACKUP plugin to be able to backup incremental backups by time (instead of log file size, right now you can FLUSH LOGS at whatever time you want...but...) -Sheeri
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
