The innodb-safe-binlog variable no longer exists, but the binlog
position is still stuffed into the innodb recovery log. Using recent
MySQL versions, does this assist the DBA when running point in time
On Fri, Jul 27, 2012 at 3:27 PM, Hartmut Holzgraefe
>> Why does InnoDB log the binlog position in its recovery log when a
>> transaction commits?
> as it needs to find out whether InnoDB state and binlog position are in
> sync during recovery?
> MySQL Internals Mailing List
> For list archives: http://lists.mysql.com/internals
> To unsubscribe: http://lists.mysql.com/internals