summaryrefslogtreecommitdiff
path: root/storage/tokudb/PerconaFT/portability/toku_crash.cc
diff options
context:
space:
mode:
authorMarko Mäkelä <marko.makela@mariadb.com>2021-04-15 11:40:43 +0300
committerMarko Mäkelä <marko.makela@mariadb.com>2021-04-15 11:40:43 +0300
commit3f8df01194700a68a62e6adbc62bd48d27dfe833 (patch)
treedd2fae41cc733fb978712c752327b9f93cc0f49d /storage/tokudb/PerconaFT/portability/toku_crash.cc
parentde746304c985b03bc3c673dc6ae1d499bb38faf9 (diff)
downloadmariadb-git-3f8df01194700a68a62e6adbc62bd48d27dfe833.tar.gz
MDEV-25425 Useless message "If the mysqld execution user is authorized page cleaner thread priority can be changed."
On startup, InnoDB tried to increase the priority of the page cleaner thread. This would usually fail, resulting in a server log message. When the page cleaner code was refactored in MDEV-23855, the throughput and latency were greatly improved even when the buf_flush_page_cleaner thread always ran the same priority with other threads in our benchmarks. So, this code should have no benefit in MariaDB Server 10.5.7 or later. Besides, starting with MariaDB Server 10.5, the executable is called mariadbd, not mysqld.
Diffstat (limited to 'storage/tokudb/PerconaFT/portability/toku_crash.cc')
0 files changed, 0 insertions, 0 deletions