Skip to content

Tags: mysqlonarm/server

Tags

mariadb-10.5.1

Toggle mariadb-10.5.1's commit message
alpha -> beta

mariadb-10.4.12

Toggle mariadb-10.4.12's commit message
List of unstable tests for 10.4.12 release

mariadb-10.3.22

Toggle mariadb-10.3.22's commit message
List of unstable tests for 10.3.22 release

mariadb-10.2.31

Toggle mariadb-10.2.31's commit message
List of unstable tests for 10.2.31 release

mariadb-10.1.44

Toggle mariadb-10.1.44's commit message
List of unstable tests for 10.1.44 release

mariadb-5.5.67

Toggle mariadb-5.5.67's commit message
Bug#29630767 - USE OF UNINITIALIZED VALUE IN LIBMYSQL (CLIENT.CC FUNC…

…TION RUN_PLUGIN_AUTH)

mariadb-10.4.11

Toggle mariadb-10.4.11's commit message
List of unstable tests for 10.4.11 release

mariadb-10.3.21

Toggle mariadb-10.3.21's commit message
List of unstable tests for 10.3.21 release

mariadb-10.2.30

Toggle mariadb-10.2.30's commit message
List of unstable tests for 10.2.30 release

mariadb-10.5.0

Toggle mariadb-10.5.0's commit message
Fix shutdown hang in dict_stats , caused by MDEV-16264

dict_stats_shutdown() can hang, waiting for timer callback to finish.
This happens because locks the same mutex, which can also used inside
timer callback, within dict_stats_schedule() function.

Fix is to make dict_stats_schedule() use mutex.try_lock() instead of
mutex.lock().

In the unlikely case of simultaneous dict_stats_schedule() setting
different timer delays, now the first one would win, which is fine.
Important is that shutdown won't hang.