Thread Previous • Date Previous • Date Next • Thread Next |
Sanja, (Resending with the mailing list since this previous conversation was there.) Please see the attached binlog files: 1. binlog_none.binlog -- No extra headers. You could generate this yourself easily, but I included it for completeness, since it otherwise matches exactly the contents of the other binlogs. 2. binlog_checksum.binlog -- With Google's checksum enabled. All non-frozen events should have an additional 4-byte header. 3. binlog_group_id.binlog -- With Google's group_id enabled. All non-frozen events should have an additional 8-byte header. 4. binlog_group_id_checksum.binlog -- With both checksum and group_id enabled. All non-frozen events should have a total of 12 bytes of additional header. Regards, Jeremy On Thu, Jul 18, 2013 at 11:19 AM, Oleksandr Byelkin <sanja@xxxxxxxxxxxxxxxx>wrote: > Hi, Jeremy! > > 18.07.2013 21:12, Jeremy Cole пишет: > > Sanja, >> >> I could provide some very simple binary logs (from Google MySQL 5.1) which >> are internally consistent and have extra headers (they would have 31-byte >> headers instead of the usual 19-byte ones). That can at least pretty >> easily >> be used to make sure mysqlbinlog can parse them properly. >> > > I'd really appreciate it. (I have no such big experience with the logs to > get some ones easy). > > >
Attachment:
binlog_checksum.binlog
Description: Binary data
Attachment:
binlog_group_id_checksum.binlog
Description: Binary data
Attachment:
binlog_group_id.binlog
Description: Binary data
Attachment:
binlog_none.binlog
Description: Binary data
Thread Previous • Date Previous • Date Next • Thread Next |