[MDEV-27460] trx_has_lock_x() gives wrong result if the table has pending table lock - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 10.6.0, 10.7(EOL), 10.8(EOL)
Fix Version/s: 10.6.6, 10.7.2, 10.8.1
Component/s: Storage Engine - InnoDB
Labels:
None

Description

In InnoDB, trx_has_lock_x() returns wrong value if other transaction has pending
lock on the table. n_lock_x_or_s can indicate the number of granter or pending
lock on the tables. This variable should be checked only to find out whether the lock
exists or not.

Attachments

Issue Links

is caused by

MDEV-25315 Assertion `ptr' failed in ut_align_down | SIGSEGV in dict_table_t::not_redundant | Assertion `!lock_sys_t::get_first(receiver_cell, receiver_id, receiver_heap_no)' failed in lock_rec_move

Closed

Activity

People

Assignee:: Thirunarayanan Balathandayuthapani

Reporter:: Thirunarayanan Balathandayuthapani

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Dates

Created:: 2022-01-10 13:39

Updated:: 2022-01-11 10:51

Resolved:: 2022-01-10 16:03

Git Integration

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