Commit Graph

11 Commits

Author SHA1 Message Date
Tianon Gravi 5ec8931249 Remove intentionally-breaking "data" symlink and add better detection
This allows for a more graceful error message for the case of users who need to update their volume path.

I tested this with 17 and `--env PGDATA=/var/lib/postgresql/17/docker` (to make sure it still works fine and doesn't complain about the extra volume provided by Docker/`VOLUME`) and 18 with `-v /var/lib/postgresql/data` (where it appropriately errors and explains to me what I should be doing instead).

I also did a reflow on some text in the error message that's designed to fit in 80 columns but was taking 81. 😂
2025-10-15 11:23:03 -07:00
Tianon Gravi 2c751341b6 Add liburing support to 18+
This is a bit complicated to use in Docker (because `io_uring` has a long and storied security story), but it is a new feature of 18+ that we should probably explicitly support for users who want to jump through the hoops to use it despite the security risk.

Additionally, this re-alphabetizes our `--with-xxx` flags.
2025-09-30 11:58:13 -07:00
Docker Library Bot 22ca5c8d8e Update 18 to 18.0, trixie 18.0-1.pgdg13+3, bookworm 18.0-1.pgdg12+3 2025-09-25 11:22:35 -07:00
Tianon Gravi a2433755c7 Update gosu to 1.19 2025-09-23 12:31:05 -07:00
Tianon Gravi a3b3bfabd3 Update gosu to 1.18 2025-09-08 13:04:25 -07:00
Docker Library Bot 5ab2c9dd1d Update 18 to 18rc1, trixie 18~rc1-1.pgdg13+1, bookworm 18~rc1-1.pgdg12+1 2025-09-04 17:02:55 -07:00
Docker Library Bot 8d2eba6040 Update 18 to 18beta3, trixie 18~beta3-1.pgdg130+1, bookworm 18~beta3-1.pgdg120+1 2025-08-14 10:31:22 -07:00
Docker Library Bot 889f9447cd Update 18 to 18beta2, bookworm 18~beta2-1.pgdg120+1, bullseye 18~beta2-1.pgdg110+1 2025-07-18 11:03:02 -07:00
Tianon Gravi 2c6fe8daca Add logic to error out on detection of "old databases" 2025-06-06 11:27:47 -07:00
Tianon Gravi b9a533c87b 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).
2025-06-06 11:27:31 -07:00
Rene Leonhardt d1e97f29ba add postgres 18 beta1 2025-06-04 15:38:23 -07:00