[MDEV-4983] Do not leave stale master-bin.info binlog state file Created: 2013-09-03  Updated: 2013-11-22  Resolved: 2013-11-22

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: None
Fix Version/s: 10.0.7

Type: Bug Priority: Major
Reporter: Kristian Nielsen Assignee: Kristian Nielsen
Resolution: Fixed Votes: 0
Labels: gtid


 Description   

The master-bin.info file records the binlog state across normal server
restarts (not crashes) to avoid the overhead of scanning last binlog file at
server start.

But we should delete the file as soon as it is read so there is no risk of
errorneously (in server code or by user) reading out-of date information from
it (eg. RESET MASTER for example).

In addition, it might be useful to read the file (if present) at server start
even if binlog files are gone (this allows to recover the binlog state even if
binlog files are intentionally omitted from a cold backup).



 Comments   
Comment by Kristian Nielsen [ 2013-11-22 ]

Pushed to 10.0-base.

Generated at Thu Feb 08 07:00:45 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.