[MDEV-14437] Document when mysql_upgrade's default for --write-binlog changed Created: 2017-11-18  Updated: 2020-08-25  Resolved: 2017-11-20

Status: Closed
Project: MariaDB Server
Component/s: Documentation
Fix Version/s: N/A

Type: Task Priority: Major
Reporter: Geoff Montee (Inactive) Assignee: Ian Gilfillan
Resolution: Fixed Votes: 0
Labels: documentation, mysql_upgrade


 Description   

mysql_upgrade's documentation says that --write-binlog is enabled by default:

--write-binlog	All commands including those run by mysqlcheck are written to the binary log. Enabled by default. Use --skip-write-binlog when commands should not be sent to replication slaves.

https://mariadb.com/kb/en/library/mysql_upgrade/#command-line-options

However, this does not seem to be the case in 10.1 or 10.2. It is disabled by default:

$ mysql_upgrade --help | grep write-binlog
 
  --write-binlog      All commands including those, issued by mysqlcheck, are
 
write-binlog                      FALSE

The documentation should probably mention which version this default changed.

 Comments   
Comment by Ian Gilfillan [ 2017-11-20 ]

Documentation updated with version information

Generated at Thu Feb 08 08:13:33 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.