Clarify init script execution order for Docker images #5179
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
Adds a note clarifying that init scripts in
/docker-entrypoint-initdb.d/execute in alphabetical order.Motivation
When using multiple init scripts with dependencies (e.g., creating materialized views that reference tables), users encounter "Unknown table" errors if scripts aren't named correctly.
This behavior comes from shell glob expansion in
entrypoint.sh(for f in /docker-entrypoint-initdb.d/*) but wasn't documented.Changes
Added note about script execution order in Docker initialization.