diff options
| author | Marko Mäkelä <marko.makela@mariadb.com> | 2017-08-23 08:05:50 +0300 |
|---|---|---|
| committer | Marko Mäkelä <marko.makela@mariadb.com> | 2017-08-23 08:13:56 +0300 |
| commit | 825b6a354a45ec541da01ff9fad7eefd1b794001 (patch) | |
| tree | 7b11380830c8aa0612850e9f8ef65d6844da07ab | |
| parent | ef8e1a35cce36459a49b15885520f740d6a55401 (diff) | |
| download | mariadb-git-825b6a354a45ec541da01ff9fad7eefd1b794001.tar.gz | |
MDEV-13452 Assertion `!recv_no_log_write' failed at startup
The previous fix (commit dcdc1c6d09b4a49b13fa8b1448064110bc296f86)
should have removed the assertion from log_close(), because every
caller that requires this assertion is already asserting that log
writes are allowed. When fil_names_clear() is called, it must be
able to write the MLOG_CHECKPOINT records. The purpose of the debug
variable recv_no_log_write is to prevent the creation of page-level
redo log records, or modifications to persistent data.
| -rw-r--r-- | storage/innobase/log/log0log.cc | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/storage/innobase/log/log0log.cc b/storage/innobase/log/log0log.cc index 7d616ca8ad8..0d0e84ab555 100644 --- a/storage/innobase/log/log0log.cc +++ b/storage/innobase/log/log0log.cc @@ -484,7 +484,6 @@ log_close(void) lsn_t checkpoint_age; ut_ad(log_mutex_own()); - ut_ad(!recv_no_log_write); lsn = log->lsn; |