Support PostgreSQL 18

[BeyondVertical]

Description of the feature Please support PostgreSQL 18

Benftits of feature We can use the latest version and have backups. Everyone is happy. Yeah!

Additional context Current output: pg_dump: detail: server version: 18.0 (Debian 18.0-1.pgdg13+3); pg_dump version: 17.5

[tlex]

Looks like until https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/91261 is merged, there is no (easy) way to do this, since there are no packages for alpine.

[tlex]

A workaround, in the meanwhile, could be building a custom image:

FROM public.ecr.aws/docker/library/postgres:18.0-alpine@sha256:f898ac406e1a9e05115cc2efcb3c3abb3a92a4c0263f3b6f6aaae354cbb1953a AS pgsql
FROM ghcr.io/tiredofit/docker-db-backup:4.1.21@sha256:36e7888e4887e57e3ab3ec5ecd4782f345226084df6d3fdd93b2d3e4a2162274

RUN set -ex; \
    mkdir -p /usr/libexec/postgresql18; \
    rm -f /usr/libexec/postgresql; \
    ln -sf /usr/libexec/postgresql18 /usr/libexec/postgresql

COPY --from=pgsql /usr/local/bin/* /usr/libexec/postgresql18/

[joshbarry92]

Looks like this blocker was merged in - is there any timeline on this being supported now?

[agjini]

I'm not sure to understand? What is the status of supporting postgres 18 ?

I'm currently using : tiredofit/db-backup | Version 4.1.21 Type 'image_changelog' for details

Thanks for this amazing tool !

[tlex]

Should be possible to support it, considering this:

$ docker run --rm -it alpine:3.23 apk add postgresql18
( 1/19) Installing postgresql-common (1.2-r2)
[...snip...]
(19/19) Installing postgresql18 (18.1-r0)
Executing postgresql18-18.1-r0.post-install
*
* If you want to use JIT in PostgreSQL, install postgresql18-jit or
* postgresql-jit (if you didn't install specific major version of postgresql).
*
Executing busybox-1.37.0-r29.trigger
Executing postgresql-common-1.2-r2.trigger
* Setting postgresql18 as the default version
OK: 41 MiB in 35 packages

I wanted to make a PR, but it requires first an update of https://github.com/tiredofit/docker-alpine, to switch to alpine:3.23

Going to ping @tiredofit for awareness.

[tiredofit]

I've been in the process behind the scenes rebuilding many of my images, and db-backup is one of them still on the list. In coming weeks I anticipate an update. There are a few barriers right now:

• I haven't updated my base images (tiredofit/alpine) since May, I have been migrating things over to a new namespace (nfrastack/base) finishing off work that has been outstanding for a few years. I don't plan on updating those base versions anymore, unless there is a security issue that is identified that any of the remaining "tiredofit" images are going to have to remain as is.
• In the past I have gone about compiling a version of Postgresql into the image to catch up before the underlying base operating system release catches up (Alpine 3.23). It's enough work right now where I personally don't have the time for as I focus on my personal support contracts.
• Alpine 3.23 currently has issues with building with Github Actions so no aarch64 images are able to be generated, and those are required in order for my continuous integration scripts to work for new releases.