Bug #77438 Extend RESET MASTER to allow specifying next binary log.
| Submitted: | 22 Jun 2015 15:46 | Modified: | 12 Feb 2018 7:36 |
|---|---|---|---|
| Reporter: | Jean-François Gagné | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Server: Replication | Severity: | S4 (Feature request) |
| Version: | 5.7 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | replication | ||
[22 Jun 2015 15:46]
Jean-François Gagné
[23 Jun 2015 20:33]
Daniël van Eeden
Created pull request for this. https://github.com/mysql/mysql-server/pull/14
[26 Jun 2015 8:25]
Daniël van Eeden
The pull request is handled in Bug #77482
[12 Feb 2018 7:36]
MySQL Verification Team
Bug #77482 is implemented with the below change log. [16 May 2017 9:42] David Moss Thanks for your contribution, this was included in MySQL 8.0.1 and the following was added to the change log: The RESET MASTER statement has been extended to allow specification of a binary log file number. The RESET MASTER TO statement accepts an argument which specifies the index of the new binary log file to use. The purpose is to simplify failover procedures by replacing the FLUSH BINARY LOGS and PURGE BINARY LOGS TO statements with a single RESET MASTER statement. The reference manual documentation here was updated: https://dev.mysql.com/doc/refman/8.0/en/reset-master.html
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.039 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.