Feature Request: Create extension container image for e.g. CNPG

[ibotty]

PostgreSQL 18 recently gained a way to load extensions from different directories. The CNPG Kubernetes operator pioneers using these images. It would be great to build this container image on release.

I am building such an image in https://github.com/ibotty/postgres-extensions-containers/actions/workflows/build-pg_duckdb.yml but it would be nice if this were part of upstream pg_duckdb.

I can contribute to setting up CI to automatically build it.

[JelteF]

Sounds useful. That contribution is definitely welcome.

[ibotty]

I would try to build another container image in the Dockerfile.

What should the image be named and where should it be published?
CNPG uses this naming scheme for timestamped (immutable) tags

<extension-name>:<ext_version>-<timestamp>-<pg_version>-<distro>

and

<extension-name>:<ext_version>-<pg_version>-<distro>

for rolling tags.

That would be

pg_duckdb:1.0.0-202511130834-18-trixie

or

pg_duckdb:1.0.0-18-trixie

That does not really fit with the existing scheme though.

I would propose to also generate example cnpg resources that show how it can be used.

What do you think?

[JelteF]

Could we call it pg_duckdb:cnpg-{version-strings}

[JelteF]

or even make the image name pg_duckdb-cnpg:{normaltag}