-
Sven Sandberg authored
Problem: 1. When --expire_logs_days and --binlog-expire-logs-seconds are set to conflicting values, and the binary log is disabled, the warning for the conflicting values was not issued and the values were not corrected. 2. There was no warning when using either of these options when the binary log is disabled. This differs from other options that are void when the binary log is disabled, such as --binlog-format and --log-slave-updates Fix: 1. Check the conflicting values of these options even when the binary log is disabled. 2. Generate a warning if any of these options is used when the binary log is disabled.
Sven Sandberg authoredProblem: 1. When --expire_logs_days and --binlog-expire-logs-seconds are set to conflicting values, and the binary log is disabled, the warning for the conflicting values was not issued and the values were not corrected. 2. There was no warning when using either of these options when the binary log is disabled. This differs from other options that are void when the binary log is disabled, such as --binlog-format and --log-slave-updates Fix: 1. Check the conflicting values of these options even when the binary log is disabled. 2. Generate a warning if any of these options is used when the binary log is disabled.
Loading