Try to open a DuckDB file from two processes at once and you get this:
_duckdb.IOException: IO Error: Could not set lock on file "server.duckdb": Conflicting lock is held in /usr/bin/python3.11 (PID 1355).
Enter fullscreen mode
Exit fullscreen mode
That has been true since the beginning. DuckDB is an in-process database: one file, one writer, full stop. DuckDB 2.0, which went GA on 21 October 2026, ships an extension called quack that turns a running DuckDB process into a small network server other DuckDB processes can connect to. I wanted to know whether that actually gets you past the lock, what it costs per query, and what it still refuses to do.
I ran DuckDB 2.0.0 through the Python client ( pip install duckdb==2.0.0 ), started a server on a table with a million rows, and hit it from separate Python processes acting as independent clients.
Setting it up
The server side loads the extension and calls quack_serve :
con = duckdb . connect ( 'server.duckdb' ) con .…