[MDEV-31489] Strange occurance of Deadlocks while using different where clause Created: 2023-06-16 Updated: 2023-06-16 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | Data Manipulation - Insert, Storage Engine - InnoDB |
| Affects Version/s: | 10.5.18, 10.11.2, 11.0.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Alexey | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Ubuntu 22.04.1 LTS |
||
| Attachments: |
|
| Description |
|
I have a table created with this query.
This table contains data:
When I am trying to run two queries at the same time from the different connections I've got Deadlock.
Console2:
After transaction is started I am running the following in both consoles:
But if I use a=0 or for example a='v' in WHERE clause deadlock doesn't occur. I attached docker-compose and test.sh script to demonstrate this issue.
And you will get something like
But
will print
|
| Comments |
| Comment by Alexey [ 2023-06-16 ] |
|
This strange behavior occurred on mariadb and mysql of all versions. |