Force-drop database before tests #3062
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It's currently very annoying to run the tests while simultaneously poking around in the database because Postgres doesn't allow databases with other active connections to be dropped. In my case, I almost always forget to terminate my connection prior to running the tests and have to re-run the test suite as a result multiple times per day. By adding the
FORCEoption, the test suite can proceed while other connections are active. Those connections will be terminated and can be restarted once developers want to go back to exploring the database manually.