Update PostgreSQL tmpfs mount for Postgres 18+ compatibility#11
Merged
ame-axelor merged 1 commit intoaxelor:devfrom Mar 17, 2026
Merged
Update PostgreSQL tmpfs mount for Postgres 18+ compatibility#11ame-axelor merged 1 commit intoaxelor:devfrom
ame-axelor merged 1 commit intoaxelor:devfrom
Conversation
ame-axelor
force-pushed
the
data-mount-pg-18
branch
from
a696a92 to
c500b2a
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
2 participants
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.
The E2E tests were failing to start the PostgreSQL container, resulting in a hang.
This is due to a breaking change in PostgreSQL 18.x container images regarding how data directories are handled.
Specifically,
postgres:alpine(which now defaults to PostgreSQL 18.x) expects the data mount to be at/var/lib/postgresqlrather than/var/lib/postgresql/data.Relevant Issues/References: