Re: question about the innodb recovery log

Percona might have background on this. This was relevant in the past,
not sure if it is still relevant:
http://bugs.mysql.com/bug.php?id=34058

See this too --
https://www.google.com/search?sourceid=navclient&hl=en&q=percona+innodb+prints+binlog+position

On Tue, Jul 31, 2012 at 8:28 AM, Rich Prohaska <[email protected]> wrote:
> Hello,
> 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
> recovery?
> Thanks
>
> On Fri, Jul 27, 2012 at 3:27 PM, Hartmut Holzgraefe
> <[email protected]> wrote:
>>> 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?
>>
>> See
>> http://dev.mysql.com/doc/refman/5.0/en/server-options.html#option_mysqld_innodb-safe-binlog
>>
>> --
>> hartmut
>>
>> --
>> MySQL Internals Mailing List
>> For list archives: http://lists.mysql.com/internals
>> To unsubscribe:    http://lists.mysql.com/internals
>>
>
> --
> MySQL Internals Mailing List
> For list archives: http://lists.mysql.com/internals
> To unsubscribe:    http://lists.mysql.com/internals
>



-- 
Mark Callaghan
[email protected]

-- 
MySQL Internals Mailing List
For list archives: http://lists.mysql.com/internals
To unsubscribe:    http://lists.mysql.com/internals