Local postgresql with custom dynamic database support for development+CI #9022
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.
I've used the local postgres startup script from #8784 and updated with the following:
package:postgres).timeoutcommand to auto-kill the process (and with that the docker container) after the specified time (6 hours).With that, the local postgres instance can be auto-started by tests or local development, and it will automatically clean up after itself.
I've updated the initalization code to probe the network port, and if it exists, it will not run the startup script (it has some overhead otherwise). A future change may also test the socket for connections.
Each local test creates its own database, which is then deleted after the test has completed its run (the scope exists).