Run /docker-entrypoint-initdb.d/*.sql scripts as $POSTGRES_USER #82
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 PR changes the entrypoint to run any
/docker-entrypoint-initdb.d/*.sql
scripts as$POSTGRES_USER
. Previously, the scripts were always run aspostgres
(which is the default for$POSTGRES_USER
, so nothing changes in the default case).Since
$POSTGRES_USER
is givenSUPERUSER
privileges in the entrypoint, that user should be able to do anythingpostgres
can do. I tested having it create a database and a role, both of which worked despite the fact thatCREATEDB
andCREATEROLE
are not granted explicitly.Fixes #81