Repository navigation
Move PostgreSQL 14-17 images to PostGIS 3.6 on Debian trixie - #81
Open
CyberNativeAI wants to merge 1 commit into
Open
CyberNativeAI wants to merge 1 commit into
CyberNativeAI wants to merge 1 commit into
Conversation
postgis/postgis moved all Debian images to trixie with PostGIS 3.6 on
2026-10-18 and no longer updates the bullseye-based *-3.5 tags. Those
frozen images still list apt.postgresql.org bullseye-pgdg, which the
PostgreSQL apt repository removed at the end of September 2026, so
`apt update` in every 14-17 Dockerfile now fails with exit code 100
("does not have a Release file").
Generate 14-17 the same way as 18: trixie-slim in update.sh, folders
renamed to {14..17}-3.6-*, Boost 1.83 and libpqxx 7.10, the osmium tool
build skipped as on 18. pgRouting versions and source hashes are
unchanged. The CI matrix now builds 3.6 for every PostgreSQL major.
extra: pin libpqxx-dev to the libpqxx series the image installs
(7.10 on trixie). trixie-pgdg now ships libpqxx-dev 8.0, whose C++20
headers osm2pgrouting 3.0.0 does not build against; this already
breaks the 18-3.6-* extra images on master.
|
Important Review skippedToo many files! This PR contains 158 files, which is 58 over the limit of 100. To get a review, reduce the PR to 100 files or fewer by splitting it into smaller PRs or changing its base branch. Upgrade to a paid plan to raise the limit. This review couldn't start because sufficient usage credits or metered capacity aren't available. Add credits or update usage-based reviews in the billing tab, then retry. ⚙️ Run configuration
📒 Files selected for processing: 158
You can disable this status message by setting the
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The PostgreSQL 14–17 images no longer build. Every
14-3.5-*to17-3.5-*Dockerfile stops atapt update:That is
make build VERSION=16-3.5-4.0on master (3219a27) today. Two upstream changes cause it:bullseye-pgdgto apt-archive.postgresql.org at the end of September (announcement). Thepostgis/postgis:*-3.5images are based on Debian bullseye and still list that suite in/etc/apt/sources.list.d/pgdg.list.*-3.5tags (docker-postgis commit 148ce95, announced in docker-postgis issue 462).This PR generates 14–17 the way this repo already generates 18:
update.sh:trixie-slimfor 14–17. Running it gives Boost 1.83, libpqxx 7.10 and the skipped osmium tool build inextra/, exactly as for 18.{14..17}-3.5-*→{14..17}-3.6-*and regenerated. pgRouting versions, tarball SHA256s and the main/develop commit hashes are unchanged. The daily "Update hashes and versions" job (Update hashes and versions #79) regenerates the new folders after this is merged. Apart from the PostgreSQL major and those pinned values, every generated file is identical to its18-3.6-*sibling.extra/:libpqxx-devis pinned to the libpqxx series the image already installs (libpqxx-dev=7.10.*on trixie, from%%PQXX_VERSION%%). trixie-pgdg now shipslibpqxx-dev8.0.2, which takes priority over Debian's 7.10.0-2. Its headers need C++20 (std::source_location), and osm2pgrouting 3.0.0 doesn't compile against it (error: no matching function for call to 'pqxx::connection::connection(std::string&)'). This already breaks the18-3.6-*extra images on master, so the pin also applies to 18.excludelist goes away.Makefile:LATEST_VERSION=17-3.6-3.7.17-3.6-3.7/17-3.6-3.8rows that were already listed (their folders were removed in d33528a) are now real again, so the duplicates are dropped.Image tags change from
N-3.5-xtoN-3.6-x, the same move docker-postgis made. The existingN-3.5-xtags on Docker Hub stay as they are.Tested with the CI steps (
make build,make test) on a local Docker host:make build(image + extra)make test16-3.5-4.0apt update(above)18-3.6-4.014-3.6-3.7(pgRouting 3.7.3)osm2pgrouting --version3.0.016-3.6-4.0(pgRouting 4.0.1)osm2pgrouting --version3.0.018-3.6-4.0(pgRouting 4.0.1)osm2pgrouting --version3.0.0The 6 tests are the official-images suite plus
pgrouting-basics, run bymake test. We did not build the other 17 combinations or the main/develop images locally. Their Dockerfiles differ from the tested ones only in the PostgreSQL major and the pinned pgRouting version, and the PR's CI matrix builds all of them.Existing data volumes (a volume created with the published
pgrouting/pgrouting:16-3.5-4.0, started under the new16-3.6-4.0.1):The server starts, and pgRouting 4.0.1 returns the same
pgr_dijkstraresult as before. Two things need the user's attention, both standard for a PostGIS minor and Debian major change:postgisextension stays at 3.5.2 untilSELECT postgis_extensions_upgrade();is run in each database that uses it.database "gis" has a collation version mismatchon every database, includingpostgres.REINDEX DATABASE <db>;followed byALTER DATABASE <db> REFRESH COLLATION VERSION;clears it.The new tag names mean nobody gets this change without choosing it. A short note in the README could help users who move an existing volume; we left that out so you can choose the wording.
Prepared by CyberNative AI LLC, an AI-run company, using AI agents.