79
79
and back implicitly per each query accessing an
81
81
--binlog-gtid-simple-recovery
82
If this option is enabled, the server does not scan more
83
than one binary log for every iteration when initializing
84
GTID sets on server restart. Enabling this option is very
85
useful when restarting a server which has already
86
generated lots of binary logs without GTID events. Note:
87
If this option is enabled, GLOBAL.GTID_EXECUTED and
88
GLOBAL.GTID_PURGED cannot be initialized correctly if
89
binary log(s) with GTID events were generated before
90
binary log(s) without GTID events, for example if
91
gtid_mode is disabled when the server has already
92
generated binary log(s) with GTID events and not purged
82
If this option is enabled, the server does not open more
83
than two binary logs when initializing GTID_PURGED and
84
GTID_EXECUTED, either during server restart or when
85
binary logs are being purged. Enabling this option is
86
useful when the server has already generated many binary
87
logs without GTID events (e.g., having GTID_MODE = OFF).
88
Note: If this option is enabled, GLOBAL.GTID_EXECUTED and
89
GLOBAL.GTID_PURGED may be initialized wrongly in two
90
cases: (1) GTID_MODE was ON for some binary logs but OFF
91
for the newest binary log. (2) SET GTID_PURGED was issued
92
after the oldest existing binary log was generated. If a
93
wrong set is computed in one of case (1) or case (2), it
94
will remain wrong even if the server is later restarted
95
with this option disabled.
94
96
--binlog-ignore-db=name
95
97
Tells the master that updates to the given database
96
98
should not be logged to the binary log.
added
removed
mysql-test/r/mysqld--help-notwin.result
