[MDEV-17545] Predicate lock for SPATIAL INDEX should lock non-matching record Created: 2018-10-25 Updated: 2018-10-25 Resolved: 2018-10-25 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB |
| Affects Version/s: | 10.2.2, 10.3.0 |
| Fix Version/s: | 10.3.11, 10.2.19 |
| Type: | Bug | Priority: | Major |
| Reporter: | Marko Mäkelä | Assignee: | Marko Mäkelä |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | gis, lock, upstream | ||
| Issue Links: |
|
||||||||
| 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. |