maria-developers team mailing list archive

[worklog-noreply@xxxxxxxxxxxx]

-----------------------------------------------------------------------
                              WORKLOG TASK
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
TASK...........: status variables for last InnoDB binlog position
CREATION DATE..: Tue, 29 Mar 2011, 09:06
SUPERVISOR.....: 
IMPLEMENTOR....: 
COPIES TO......: 
CATEGORY.......: Server-RawIdeaBin
TASK ID........: 191 (http://askmonty.org/worklog/?tid=191)
VERSION........: Server-9.x
STATUS.........: Un-Assigned
PRIORITY.......: 60
WORKED HOURS...: 0
ESTIMATE.......: 0 (hours remain)
ORIG. ESTIMATE.: 0

PROGRESS NOTES:



DESCRIPTION:

In every commit, InnoDB/XtraDB stores the binlog position in the system
tablespace (in a transactional-safe way).

At server start, this position is printed to the error log.

This is useful after taking a backup to provision a slave, as it provides the
values to use for CHANGE MASTER TO.

It would be useful if these values printed to the error log were also directly
available to SQL as read-only status variables:

    innodb_startup_binlog_master_file
    innodb_startup_binlog_master_pos

This would be generally useful.

When this is implemented, the test case main.group_commit_binlog_pos can be
fixed to not require `grep` and `tail`, and so work on Windows with no posix
tools installed.


ESTIMATED WORK TIME

ESTIMATED COMPLETION DATE
-----------------------------------------------------------------------
WorkLog (v4.0.0)