Serious bug in Azure Database for PostgreSQL Flexible Server PostGIS extension

Martin Daly 0 Reputation points
2025-08-21T16:03:55.86+00:00

The Azure Database for PostgreSQL Flexible Server instances that we have were upgraded over the weekend (on Saturday 16th, as far as I can tell).

The upgrade has introduced a new version of the PostGIS extension that we rely on. You can see from this page that all versions of the PostgreSQL database in Azure now use PostGIS version 3.5.2:

https://learn.microsoft.com/en-us/azure/postgresql/extensions/concepts-extensions-versions#postgis

PostGIS versions 3.5.0, 3.5.1 and 3.5.2 all have a serious bug that can, and is, affecting our users. We reported this bug to the PostGIS developers in December 2024, and it was fixed in March 2025:

https://trac.osgeo.org/postgis/ticket/5819

The first version with the fix is PostGIS 3.5.3 (released in May 2025):

https://git.osgeo.org/gitea/postgis/postgis/raw/tag/3.5.3/NEWS

See this entry from the NEWS, with matching ticket number: "- #5819, Support longer names in estimated extent (Paul Ramsey)"

This bug is serious, and the supported version of PostGIS needs to be upgraded to 3.5.3 (or downgraded to 3.4.x) as a matter of urgency.How can we make this happen?

Azure Database for PostgreSQL
{count} votes

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.