[MDEV-34877] Port "Bug #11745929 Change lock priority so that the transaction holding S-lock gets X-lock first" fix from MySQL to MariaDB - Jira

XML

Word

Printable

Details

Type: Bug
Status: In Progress (View Workflow)
Priority: Major
Resolution: Unresolved
Affects Version/s: 10.5, 10.6, 10.11, 11.1(EOL), 11.2, 11.4, 11.6, 11.7, 10.8(EOL), 10.9(EOL), 10.10(EOL), 11.0(EOL), 11.3(EOL), 11.5(EOL)
Fix Version/s: 10.5, 10.6, 10.11, 11.2, 11.4, 11.6, 11.7
Component/s: Storage Engine - InnoDB
Labels:
- zabbix

Description

~~MDEV-27025~~ describes the following case:
1. trx1 gets an S-lock granted
2. trx2 wants an X-lock, but has to wait for trx1
3. trx1 now wants an X-lock, but waits for trx2

The try to fix ~~MDEV-27025~~ caused ~~MDEV-27992~~, what made us to revert ~~MDEV-27025~~ fix(see also this comment). It seems, MySQL's "Bug #11745929" fix solves ~~MDEV-27025~~ issue.

Attachments

Issue Links

relates to

MDEV-27025 insert-intention lock conflicts with waiting ORDINARY lock

Closed

Activity

People

Assignee:: Vladislav Lesin

Reporter:: Vladislav Lesin

Votes:: 0 Vote for this issue

Watchers:: 6 Start watching this issue

Dates

Created:: 2024-09-05 10:06

Updated:: 5 days ago 14:07

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.