You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
does it support concurrent read?
If i try to read same table from two different processes, one of the processes will fail.
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The text was updated successfully, but these errors were encountered:
@alitrack , it does seem like duckdb does support multiple concurrent reads from different processes if a read only flag is set. duckdb/duckdb#1343
I am experiencing the same problem as others have reported where the duckdb database file is in use by another connection. I am nor sure how difficult it would be to implement, but just a suggestion that it would be great if the create server command had an option to specify connections should be read only. Maybe it would then be possible to have a single foreign server created that has a writeable connection and another that is read only. That way, one could still import data, create tables and make changes to the duckdb database using one foreign server reference and other users could still access the database using the foreign server that only has read only connections.
SQL Error [HV00N]: ERROR: failed to open SQLite DB. rc=1 path=/data/postgres/duckdb/sds.db
does it support concurrent read?
If i try to read same table from two different processes, one of the processes will fail.
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The text was updated successfully, but these errors were encountered: