fix: build PostGIS from the stable-3.6 branch#128
Merged
NiccoloFei merged 1 commit intomainfrom Apr 24, 2026
Merged
Conversation
NiccoloFei
requested review from
fcanovai,
gbartolini,
jbattiato,
litaocdl,
mnencia and
sxd
as code owners
Signed-off-by: Niccolò Fei <niccolo.fei@enterprisedb.com>
NiccoloFei
force-pushed
the
dev/pin-postgis
branch
from
6247057 to
3ec4a7d
Compare
mnencia
approved these changes
Apr 24, 2026
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
2 participants
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.
Build PostGIS using
stable-3.6instead ofmain.The
mainbranch has moved theaddress_standardizerextension into a separate https://github.com/postgis/address_standardizer repository.When building
address_standardizerfrom its new repository, the library is being created asaddress_standardizer.so, while inv18packages the extension was calledaddress_standardizer-3.so.This makes pg_upgrade complain with:
As a workaround, pin
PostGIStostable-3.6until we have a solution.