Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.11.8
-
Debian Bookworm
Description
The following stack trace had to wait on dict_sys.latch:
ssux_lock_impl<false>::rd_wait()
|
dict_table_open_on_name(char const*, bool, dict_err_ignore_t)
|
dict_stats_update(dict_table_t*, dict_stats_upd_option_t)
|
ha_innobase::info_low(unsigned int, bool)
|
ha_innobase::open(char const*, int, unsigned int)
|
handler::ha_open(TABLE*, char const*, int, unsigned int, st_mem_root*, List<String>*)
|
(According to Marko Mäkelä: ) This one is an InnoDB bug. We certainly should not acquire and release a shared dict_sys.latch within a single ha_innobase::open().
Attachments
Issue Links
- relates to
-
MDEV-35000 dict_table_close() is a performance hog
- Open
-
MDEV-34988 InnoDB locks dict_sys.latch for a long time during ALTER TABLE
- Open