[MDEV-25210] why sub query need LOCK_R when SQLCOM_UPDATE_MULTI ? Created: 2021-03-20 Updated: 2021-03-24 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB |
| Affects Version/s: | 10.4.8 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | chu huaxing | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
READ-COMMITTED: innodb READ-COMMITTED: table:
case 1:
case 2:
why SQLCOM_UPDATE_MULTI can‘t be LOCK_NONE ? |
| Comments |
| Comment by chu huaxing [ 2021-03-22 ] |
|
must it to lock with LOCK_S for test_sharding1 in sql (update test_sharding a inner join (select key1 from test_sharding1) b on a.key1=b.key1 set a.key2=111 |