diff options
| author | Alfranio Correia <alfranio.correia@sun.com> | 2009-06-11 02:08:40 +0100 |
|---|---|---|
| committer | Alfranio Correia <alfranio.correia@sun.com> | 2009-06-11 02:08:40 +0100 |
| commit | dd59815f59be26b998d52b82a8c5f3e53e637c99 (patch) | |
| tree | f5ad78fe4c7b539a42adb5252a243809c0380676 /sql/set_var.cc | |
| parent | afacea4d602bd2230791bd7a91f51e380e00f5d0 (diff) | |
| download | mariadb-git-dd59815f59be26b998d52b82a8c5f3e53e637c99.tar.gz | |
BUG#34687 Error in bin-log after shutdown restart binlog was not closed properly
While reading a binary log that is being used by a master or was not properly
closed, most likely due to a crash, the following warning message is being
printed out: "Warning: this binlog was not closed properly. Most probably mysqld
crashed writing it.". This was scaring our users as the message was not taking
into account the possibility of the file is being just used by the master.
To avoid unnecessarily scaring our users, we replace the original message by the
following one: Warning: "this binlog is either is use or was not closed properly.".
Diffstat (limited to 'sql/set_var.cc')
0 files changed, 0 insertions, 0 deletions