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
Currently, we kill all database connections (more specifically, the user sessions) when we try to drop a database. While we do not need to check if a database exists, we might end up with non-user sessions that are still connected to the database after the kill command that prevent the drop of the database. We should switch to using SET SINGLE USER WITH ROLLBACK IMMEDIATE instead.
The text was updated successfully, but these errors were encountered:
Currently, we kill all database connections (more specifically, the user sessions) when we try to drop a database. While we do not need to check if a database exists, we might end up with non-user sessions that are still connected to the database after the kill command that prevent the drop of the database. We should switch to using
SET SINGLE USER WITH ROLLBACK IMMEDIATE
instead.The text was updated successfully, but these errors were encountered: