-
-
Notifications
You must be signed in to change notification settings - Fork 19
Open
Description
Hi there,
We’ve been using GizmoSQL with a DuckDB backend and have encountered an issue where DuckDB occasionally crashes. When this happens, the database server enters safe mode and returns the following error:
FATAL Error:
Failed: database has been invalidated because of a previous fatal error.
The database must be restarted prior to being used again.
DuckDB Doc: https://duckdb.org/docs/stable/guides/troubleshooting/crashes.html#types-of-crashes
As the error message indicates, the database must be restarted before it can be used again. However, my application server continues to receive this error because GizmoSQL propagates the underlying error back to the client.
Is there a way to automatically trigger a restart when this error occurs? Alternatively, can GizmoSQL be configured to reinitialize DuckDB in such cases?
Any guidance would be greatly appreciated.
Thanks in advance!
Metadata
Metadata
Assignees
Labels
No labels