[MDEV-17545] Predicate lock for SPATIAL INDEX should lock non-matching record - Jira

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 10.2.2, 10.3.0
Fix Version/s: 10.3.11, 10.2.19
Component/s: Storage Engine - InnoDB
Labels:
- gis
- lock
- upstream

Description

Bug 27577612 - CONCURRENT SERIALIZABLE TRANSACTIONS CAN INSERT INTO AN AREA SELECTED FOR UPDATE fixes an ACID bug for SPATIAL INDEX.

Their test case passes also without the fix present, presumably because a locking conflict will exist also on the clustered index. So, we cannot add their test case.

Attachments

Issue Links

blocks

MDEV-17536 Merge new release of InnoDB 5.7.24 to 10.2

Closed

Activity

Ascending order - Click to sort in descending order

Marko Mäkelä created issue - 2018-10-25 12:13

Marko Mäkelä made changes - 2018-10-25 12:13

Field	Original Value	New Value
Link		This issue blocks ~~MDEV-17536~~ [ ~~MDEV-17536~~ ]

Marko Mäkelä made changes - 2018-10-25 14:18

issue.field.resolutiondate

2018-10-25 14:18:52.0

2018-10-25 14:18:52.432

Marko Mäkelä made changes - 2018-10-25 14:18

Resolution		Fixed [ 1 ]
Status	Open [ 1 ]	Closed [ 6 ]

Sergei Golubchik made changes - 2021-12-06 21:48

Workflow

MariaDB v3 [ 90245 ]

MariaDB v4 [ 155108 ]

People

Assignee:: Marko Mäkelä

Reporter:: Marko Mäkelä

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Dates

Created:: 2018-10-25 12:13

Updated:: 2018-10-25 14:18

Resolved:: 2018-10-25 14:18

Git Integration

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

MariaDB Server