diff options
| author | Marko Mäkelä <marko.makela@mariadb.com> | 2021-01-06 13:53:14 +0200 |
|---|---|---|
| committer | Marko Mäkelä <marko.makela@mariadb.com> | 2021-01-06 13:53:14 +0200 |
| commit | a9933105938d4d809ea33ac3196e681cd581374f (patch) | |
| tree | 153be157e073fe09bf6d6298f4c27c1ffb0ec79b /mysql-test/suite/innodb/r/foreign-keys.result | |
| parent | 02e7bff882c5169ba3e1ce7e9a93d4c28fe3afd1 (diff) | |
| download | mariadb-git-a9933105938d4d809ea33ac3196e681cd581374f.tar.gz | |
MDEV-24537 innodb_max_dirty_pages_pct_lwm=0 lost its special meaning
In commit 3a9a3be1c64b14c05648e87ebe0f1dd96457de41 (MDEV-23855)
some previous logic was replaced with the condition
dirty_pct < srv_max_dirty_pages_pct_lwm, which caused
the default value of the parameter innodb_max_dirty_pages_pct_lwm=0
to lose its special meaning: 'refer to innodb_max_dirty_pages_pct instead'.
This implicit special meaning was visible in the function
af_get_pct_for_dirty(), which was removed in
commit f0c295e2de8c074c2ca72e19ff06e1d0e3ee6d2b (MDEV-24369).
page_cleaner_flush_pages_recommendation(): Restore the special
meaning that was removed in MDEV-24369.
buf_flush_page_cleaner(): If srv_max_dirty_pages_pct_lwm==0.0,
refer to srv_max_buf_pool_modified_pct. This fixes the observed
performance regression due to excessive page flushing.
buf_pool_t::page_cleaner_wakeup(): Revise the wakeup condition.
innodb_init(): Do initialize srv_max_io_capacity in Mariabackup.
It was previously constantly 0, which caused mariadb-backup --prepare
to hang in buf_flush_sync(), making no progress.
Diffstat (limited to 'mysql-test/suite/innodb/r/foreign-keys.result')
0 files changed, 0 insertions, 0 deletions