-
Notifications
You must be signed in to change notification settings - Fork 0
Comparing changes
Open a pull request
base repository: reneleonhardt/postgres-docker
base: master
head repository: docker-library/postgres
compare: master
- 7 commits
- 57 files changed
- 3 contributors
Commits on Jun 4, 2025
-
Configuration menu - View commit details
-
Copy full SHA for d1e97f2 - Browse repository at this point
Copy the full SHA d1e97f2View commit details
Commits on Jun 6, 2025
-
Merge pull request docker-library#1344 from reneleonhardt/chore/add-p…
…ostgres-18 chore: add postgres 18 beta1
Configuration menu - View commit details
-
Copy full SHA for c257dcc - Browse repository at this point
Copy the full SHA c257dccView commit details -
Change
PGDATA
in 18+ to/var/lib/postgresql/MAJOR/docker
This is a pretty large breaking change, which is why this only makes the change in 18+ (which is currently in pre-release stages, and not due for GA until September, and pre-release `PGDATA` directories are officially *not supported* on the GA release anyhow). Concretely, this changes `PGDATA` to `/var/lib/postgresql/MAJOR/docker`, which matches the pre-existing convention/standard of the `pg_ctlcluster`/`postgresql-common` set of commands, and frankly is what we should've done to begin with, in a classic case of Chesterton's Fence (https://en.wikipedia.org/wiki/Wikipedia:Chesterton%27s_fence). This also changes the `VOLUME` to `/var/lib/postgresql`, which should be more reasonable, and make the upgrade constraints more obvious. For any users who have been testing the pre-releases, the simplest way to keep your existing data directory is going to be to add `PGDATA=/var/lib/postgresql/data` as an environment variable on your container or adjust your bind-mount from `/var/lib/postgresql/data` to `/var/lib/postgresql/18/docker`, but the *best* way is going to be to refactor your host directory such that your data lives at `18/docker` inside and you can then mount directly to `/var/lib/postgresql` (possibly setting `PGDATA=/var/lib/postgresql/MAJOR/docker` as well, if you want to go overboard on being explicit).
Configuration menu - View commit details
-
Copy full SHA for b9a533c - Browse repository at this point
Copy the full SHA b9a533cView commit details -
Configuration menu - View commit details
-
Copy full SHA for 2c6fe8d - Browse repository at this point
Copy the full SHA 2c6fe8dView commit details -
Merge pull request docker-library#1259 from infosiftr/pgdata-cluster
Change `PGDATA` in 18+ to `/var/lib/postgresql/MAJOR/docker`
Configuration menu - View commit details
-
Copy full SHA for 6ec0e42 - Browse repository at this point
Copy the full SHA 6ec0e42View commit details
Commits on Jun 9, 2025
-
Only install 18+ JIT package on architectures where it's supported
See: - https://salsa.debian.org/postgresql/postgresql/-/commit/eaa9529d8ecb0beaeebeb5b09362dbdf4ce34c0c "Make LLVM architectures a inclusion list so it works in the Architecture field." (which removes i386, notably) - https://salsa.debian.org/postgresql/postgresql/-/commit/1d6f624592d18d0cb0d694675037984f0d44b5ae "Disable JIT on loong64 and riscv64 again, still segfaulting."
Configuration menu - View commit details
-
Copy full SHA for 46e8474 - Browse repository at this point
Copy the full SHA 46e8474View commit details -
Merge pull request docker-library#1345 from infosiftr/conditional-jit
Only install 18+ JIT package on architectures where it's supported
Configuration menu - View commit details
-
Copy full SHA for 38b3c10 - Browse repository at this point
Copy the full SHA 38b3c10View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff master...master