There is a concurrency bug in "Multiple concurrent updaters" that gets triggered at times
Hi, any progress on this bug? We want to test concurrency with DuckDB and it's not clear whether it is safe to use DuckDB for concurrent queries. Our queries are read-only queries though, which may help.
I have not looked at it yet, but I will take a look at it this week. Read-only queries should have no problems, the bug is related to concurrent UPDATE statements.
have not seen this one in a while, it might be fixed?
This issue should be fixed in the buffermanager branch, it is still present in the master branch though.
This issue has been fixed now that the buffermanager branch has been merged