fix: add database name to postgres healthcheck#203
Open
keithy wants to merge 1 commit intonextlevelbuilder:mainfrom
Open
fix: add database name to postgres healthcheck#203keithy wants to merge 1 commit intonextlevelbuilder:mainfrom
keithy wants to merge 1 commit intonextlevelbuilder:mainfrom
Conversation
When POSTGRES_USER differs from POSTGRES_DB, pg_isready defaults to connecting to a database named after the user, causing healthcheck to fail with "database does not exist".
keithy
force-pushed
the
fix/postgres-healthcheck-db-name
branch
from
be71bb1 to
7962a3e
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
-d ${POSTGRES_DB}instead of defaulting to usernamePOSTGRES_USERdiffers fromPOSTGRES_DBTest plan
💘 Generated with Crush