Different dependencies installed for PG13 s390x, mips64le vs amd64, arm64, ppc64le (has some to PG14 rel. packages)

[Dexus]

When I running:

on amd64, arm64, ppc64le

docker run --platform=linux/amd64 -ti --rm postgres:13-bullseye bash -c "dpkg -l | grep -i postgresql"
Status: Downloaded newer image for postgres:13-bullseye
ii  libpq5:amd64              14.2-1.pgdg110+1             amd64        PostgreSQL C client library
ii  pgdg-keyring              2018.2                       all          keyring for apt.postgresql.org
ii  postgresql-13             13.6-1.pgdg110+1             amd64        The World's Most Advanced Open Source Relational Database
ii  postgresql-client-13      13.6-1.pgdg110+1             amd64        front-end programs for PostgreSQL 13
ii  postgresql-client-common  238.pgdg110+1                all          manager for multiple PostgreSQL client versions
ii  postgresql-common         238.pgdg110+1                all          PostgreSQL database-cluster manager

on s390x and mips64le it looks like

docker run --platform=linux/s390x -ti --rm postgres:13-bullseye bash -c "dpkg -l | grep -i postgresql"
ii  libpq5:s390x              13.6-1.pgdg110+1             s390x        PostgreSQL C client library
ii  pgdg-keyring              2018.2                       all          keyring for apt.postgresql.org
ii  postgresql-13             13.6-1.pgdg110+1             s390x        The World's Most Advanced Open Source Relational Database
ii  postgresql-client-13      13.6-1.pgdg110+1             s390x        front-end programs for PostgreSQL 13
ii  postgresql-client-common  238.pgdg110+1                all          manager for multiple PostgreSQL client versions
ii  postgresql-common         238.pgdg110+1                all          PostgreSQL database-cluster manager

Does this make problems?
libpq5:amd64 14.2-1.pgdg110+1 != libpq5:s390x 13.6-1.pgdg110+1

I don't want to try it!

I would expect not to have any postgres14 dependencies for the postgres 13 images

[wglambert]

Upstream only has a handful of officially built architectures

postgres/13/bullseye/Dockerfile

Lines 98 to 101 in e483778

	aptRepo="[ signed-by=/usr/local/share/keyrings/postgres.gpg.asc ] http://apt.postgresql.org/pub/repos/apt/ bullseye-pgdg main $PG_MAJOR"; \
	case "$dpkgArch" in \
	amd64 | arm64 | ppc64el) \
	# arches officialy built by upstream

Architectures not on the list are built from source

postgres/13/bullseye/Dockerfile

Lines 106 to 108 in e483778

	# we're on an architecture upstream doesn't officially build for
	# let's build binaries from their published source packages
	echo "deb-src $aptRepo" > /etc/apt/sources.list.d/pgdg.list; \

[tianon]

I'm more concerned by the s390x image getting an older version of libpq than I am by the amd64 image getting a newer one -- we're installing these directly from the PostgreSQL repositories in the way that they recommend, and I haven't ever seen a compatibility issue with having "too new" of a libpq instance.

[tianon]

Ah, we're building libpq5 as part of postgresql-XX, so we'd have to do a lot of extra work to build a newer version on these architectures -- #800 (comment) is also very relevant.

[Dexus]

Who guarantees me that the compatibility between both versions is really permanently given? Although it says on the postgesql website that it should be so, but we all know that such a thing is not 100% guaranteed.
Know I build all source new, to have the packages and created my own apt repo. But this is not the ideal way I think.