Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use SetSingleUser when dropping databases #11

Closed
feO2x opened this issue Sep 15, 2022 · 0 comments · Fixed by #12
Closed

Use SetSingleUser when dropping databases #11

feO2x opened this issue Sep 15, 2022 · 0 comments · Fixed by #12
Assignees

Comments

@feO2x
Copy link
Contributor

feO2x commented Sep 15, 2022

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.

@feO2x feO2x self-assigned this Sep 15, 2022
@feO2x feO2x linked a pull request Sep 16, 2022 that will close this issue
@feO2x feO2x closed this as completed in #12 Sep 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant