diff options
| author | Vlad Lesin <vlad_lesin@mail.ru> | 2020-05-13 14:32:12 +0300 |
|---|---|---|
| committer | Vlad Lesin <vlad_lesin@mail.ru> | 2020-05-19 11:25:56 +0300 |
| commit | 0f9bfcc323f76389eab23220d757e1cdfacb0543 (patch) | |
| tree | 0df3910f96c0d0f51c3f27c8d3596c1506fcdeaf /storage/innobase/ut/ut0ut.cc | |
| parent | a84060567c1b9c3f1efd94fabc99a40b3f91b598 (diff) | |
| download | mariadb-git-0f9bfcc323f76389eab23220d757e1cdfacb0543.tar.gz | |
MDEV-22554: "mariabackup --prepare" exits with code 0 even though innodb
error is logged
The fix is to set flag in ib::error::~error() and check it in
mariabackup.
ib::error::error() is replaced with ib::warn::warn() in
AIO::linux_create_io_ctx() because of two reasons:
1) if we leave it as is, then mariabackup MTR tests will fail with --mem
option, because Linux AIO can not be used on tmpfs,
2) when Linux AIO can not be initialized, InnoDB falls back to simulated
AIO, so such sutiation is not fatal error, it should be treated as warning.
Diffstat (limited to 'storage/innobase/ut/ut0ut.cc')
| -rw-r--r-- | storage/innobase/ut/ut0ut.cc | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/storage/innobase/ut/ut0ut.cc b/storage/innobase/ut/ut0ut.cc index 252f3a50ae1..b50735a391d 100644 --- a/storage/innobase/ut/ut0ut.cc +++ b/storage/innobase/ut/ut0ut.cc @@ -624,9 +624,13 @@ warn::~warn() sql_print_warning("InnoDB: %s", m_oss.str().c_str()); } +/** true if error::~error() was invoked, false otherwise */ +bool error::logged; + error::~error() { sql_print_error("InnoDB: %s", m_oss.str().c_str()); + logged = true; } #ifdef _MSC_VER |