Details
-
Task
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
MDL belongs to a transaction, not to a connection. For example, when a transaction is moved to a different thd, MDLs should be moved too.
Problem, what if a connection owns more than one open transaction and they have conflicting lock requests? It cannot wait on itself, so deadlock detector has to be able to detect a loop right away.
Attachments
Issue Links
- relates to
-
MDEV-21602 CREATE TABLE…PRIMARY KEY…SELECT workaround causes DROP TABLE to ignore locks
- Closed