mirror of
https://github.com/MariaDB/server.git
synced 2026-05-07 23:54:31 +02:00
Encourage user to specify a name for the binlog index file (either by giving an argument to --log-bin,
or by using --log-bin-index). This is so that he does not have a replication break when his master's hostname changes. Plus binary logging options consistency checks. sql/mysqld.cc: * Encourage user to specify a name for the binlog index file (either by giving an argument to --log-bin, or by using --log-bin-index). This is so that he does not have a replication break when his master's hostname changes. Why not a fatal error? To not break existing many-machine setups. * --log-bin-index without --log-bin does not make sense. * --log-slave-updates without --log-bin does not either. support-files/my-huge.cnf.sh: encourage providing an argument to log-bin support-files/my-innodb-heavy-4G.cnf.sh: encourage providing an argument to log-bin support-files/my-large.cnf.sh: encourage providing an argument to log-bin support-files/my-medium.cnf.sh: encourage providing an argument to log-bin support-files/my-small.cnf.sh: encourage providing an argument to log-bin
This commit is contained in:
parent
d3f5dfbd17
commit
397f3ee554
6 changed files with 39 additions and 14 deletions
|
|
@ -189,7 +189,7 @@ tmp_table_size = 64M
|
|||
# Enable binary logging. This is required for acting as a MASTER in a
|
||||
# replication configuration. You also need the binary log if you need
|
||||
# the ability to do point in time recovery from your latest backup.
|
||||
log_bin
|
||||
log-bin=mysql-bin
|
||||
|
||||
# If you're using replication with chained slaves (A->B->C), you need to
|
||||
# enable this option on server B. It enables logging of updates done by
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue