diff options
author | Guilhem Bichot <guilhem@mysql.com> | 2009-02-09 22:52:42 +0100 |
---|---|---|
committer | Guilhem Bichot <guilhem@mysql.com> | 2009-02-09 22:52:42 +0100 |
commit | 9653feb1600c84fc5e51fe102761c93b7f83de0f (patch) | |
tree | a7fbefd733111a6af98afd1f29128512c297e9f8 /sql/rpl_rli.cc | |
parent | 554eb6c2cf00d80d283374a749ca82f1a1f13bae (diff) | |
download | mariadb-git-9653feb1600c84fc5e51fe102761c93b7f83de0f.tar.gz |
Callers of translog_deassign_id_from_share() need intern_lock.
Assert that keys don't point to bitmap pages.
storage/maria/ma_blockrec.h:
assertion
storage/maria/ma_locking.c:
With concurrent INSERTs, it is possible that two threads enter _ma_mark_file_changed()
at the same time, so they should serialize their access to the "changed" state/share
members; another reason is that this function may call _ma_update_state_lsns_sub()
which may call translog_deassign_id_from_share() (I saw it during testing of
online backup) which requires the intern_lock mutex.
As INSERTs only change from "not changed" to "changed", we can first check without mutex:
if it says "changed", some other thread has set or is setting the variables now,
we don't need to do it; if it says "not changed", we serialize and re-check.
Diffstat (limited to 'sql/rpl_rli.cc')
0 files changed, 0 insertions, 0 deletions