There is a possibility for deadlock when one query queries sys.tables for the first time in that client's session (instantiating the tmp._tables temporary table), and another client updating a table that happens to have an id that has the same modulo 64 as tmp._tables.
I.e., this is pretty specific

**To Reproduce**
This is hard to reproduce since it depends on exact timing and just the right table ids.

**Expected behavior**
No deadlock, obviously.

**Screenshots**
If applicable, add screenshots to help explain your problem.


deadlock, causing new connections to hang indefinitely
This is a GitHub Issue
repo:MonetDB
owner:MonetDB
Title : deadlock, causing new connections to hang indefinitely
Issue date:

--- start body ---
There is a possibility for deadlock when one query queries sys.tables for the first time in that client's session (instantiating the tmp._tables temporary table), and another client updating a table that happens to have an id that has the same modulo 64 as tmp._tables.
I.e., this is pretty specific

**To Reproduce**
This is hard to reproduce since it depends on exact timing and just the right table ids.

**Expected behavior**
No deadlock, obviously.

**Screenshots**
If applicable, add screenshots to help explain your problem.


--- end body ---

The issue describes a potential deadlock scenario in MonetDB where two clients can cause their connections to hang indefinitely due to a specific timing condition and table ID conflicts. However, this does not constitute a security vulnerability, as it does not allow for unauthorized access or data manipulation, but rather a performance issue.