copy-back creates wrong binlog.index

Description

MySQL: 8.0.19

PXB: 8.0.9

 

When MySQL is started with the following my.cnf configuration:

 

PXB, when copy-ing back files creates wrong binlog.index:

 

 

Environment

None

AFFECTED CS IDs

274027, CS0018179

Activity

KennT May 26, 2021 at 7:37 AM
Edited

This occurs when

(1) the log-bin path is in the datadir

(2) the log-bin name uses an absolute path

In this case, we are trying to use binlog_file_location::name, which is not created correctly.

So a workaround is to have the log-bin use a relative path (it's already relative to the datadir).  So change the above configuration to "log-bin=binlog"

Done

Details

Assignee

Reporter

Time tracking

2d 3h 5m logged

Affects versions

Priority

Created February 14, 2020 at 9:58 AM
Updated March 6, 2024 at 7:03 PM
Resolved June 1, 2021 at 2:23 AM