chore: Use the pg_isready command to assess whether PostgreSQL is ready or not
#1111
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This strategy aligns with the MySQL and MariaDb wait strategies. Also, logs have changed over time and the current strategy doesn't work with older PostgreSQL Docker images (for example v9.6) which does not produce the same logs as recent versions of the PostgreSQL docker image.
✅ Deploy Preview for testcontainers-dotnet ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
HofmeisterAn
added
the
chore
HofmeisterAn
changed the title
pg_isready command to asses whether PostgreSQL is ready or notpg_isready command to assess whether PostgreSQL is ready or not
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This strategy aligns with the MySQL and MariaDb wait strategies.
Also, logs have changed over time and the current strategy doesn't work with older PostgreSQL Docker images (for example v9.6) which does not produce the same logs as recent versions of the PostgreSQL docker image.