Currently the innodb replication log (SYS_REPLICATION_LOG) table has the following layout:
id BINARY(8), message BLOB The ID field maps to the inno trx id and the MESSAGE field holds the GPB message. In Drizzle its not safe to assume that the inno trx id 2 committed before trx id 1, so having this as the primary key will cause problems, think out of order slave replay. While Im fixing that problem Id like to propose the following layout for the table modeled after http://code.google.com/p/google-mysql-tools/wiki/GlobalTransactionIds I propose the following layout: group_id, trx_id, server_id, timestamp, message group_id= increasing uint64_t value (primary key) trx_id= inno trx id server_id= id for the server timestamp= gpb end timestamp message= gpb message Opinions? other suggestions
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
