Details
-
Bug
-
Status: Confirmed (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.2.2, 10.3.0
Description
InnoDB Should skip mvcc and transaction locking for temporary tables in 10.2+. Currently row_search_mvcc() process temporary tables with locking. Temporary tables is private to
the connection. There can be one active transaction in temporary table. So it is not necessary
to use mvcc and transaction locking for temporary tables.
Attachments
Issue Links
- relates to
-
-
- Closed
-
-
-
- Closed
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Link |
This issue relates to |
| Issue Type | Task [ 3 ] | Bug [ 1 ] |
| Component/s | Storage Engine - InnoDB [ 10129 ] |
| Affects Version/s | 10.2.2 [ 22013 ] |
| Affects Version/s | 10.3.0 [ 22127 ] |
| Labels | lock performance temporary |
| Status | Open [ 1 ] | Confirmed [ 10101 ] |
| Fix Version/s | 10.3 [ 22126 ] |
| Link |
This issue relates to |
| Fix Version/s | 10.4 [ 22408 ] |
| Workflow | MariaDB v3 [ 88581 ] | MariaDB v4 [ 144059 ] |
| Fix Version/s | 10.2 [ 14601 ] |
| Fix Version/s | 10.3 [ 22126 ] |
Similarly, InnoDB should skip transactional locking for the change buffer tree. The attachment uniqstack.txt in
MDEV-16467shows that lock_update_delete() is being called via btr_cur_optimistic_delete_func() by ibuf_delete_rec(). There should be no transactions operating on the change buffer tree, hence the locking there is completely unnecessary.I would also disable the use of the adaptive hash index on temporary tables and the change buffer tree if they are not already disabled.