Re: Inquiry on planned PostGIS releases and minor-version behavior (now–Feb 28)

[Bharath Tadikonda]

 Thank you, Paul and Regina, for your responses. I really appreciate your
time and the helpful information. I’ll review this on our side and will
reach out if we need any further clarification

On Wed, Jan 21, 2026 at 2:09 PM Regina Obe <lr at pcorp.us> wrote:

> Bharath,
>
>
>
> The best advice I can give is to look at the upcoming NEWS items
>
>
>
> https://gitea.osgeo.org/postgis/postgis/src/branch/stable-3.6/NEWS
>
>
>
> and yes we most likely will do a micro release before February 28
>
>
>
>
>
> *From:* Bharath Tadikonda <tadikondabharath at gmail.com>
> *Sent:* Wednesday, January 21, 2026 1:36 PM
> *To:* postgis-users at lists.osgeo.org
> *Subject:* Inquiry on planned PostGIS releases and minor-version behavior
> (now–Feb 28)
>
>
>
> Hello PostGIS Team,
>
> I’m a PostgreSQL Database Engineer managing production PostgreSQL/PostGIS
> workloads on AWS RDS/Aurora.
>
> We are planning a PostgreSQL *minor upgrade* (PostgreSQL 16.6 → 16.11) in
> the near term. In our environment, past *PostGIS minor/patch releases*
> have occasionally caused operational issues due to changes in function
> behavior, even when PostgreSQL itself was a minor upgrade. Because AWS may
> bundle a newer PostGIS minor version along with a PostgreSQL minor upgrade,
> we want to plan and execute testing and production rollout as close
> together as possible.
>
> To help us plan safely, I wanted to ask:
>
>    1. *Are there any planned PostGIS releases (minor or patch) between
>    now and February 28?*
>
>
>    - If yes, which versions are anticipated?
>       - If not, when is the next postgis version release anticipated?
>
>
>    2. *For PostGIS minor/patch releases (e.g., 3.6.x → 3.6.y):*
>
>
>    - Are changes strictly bug fixes, or can they include behavioral
>       changes to existing functions?
>       - Are there specific classes of functions (geometry processing,
>       topology, raster, etc.) where behavior changes are more likely?
>
>
>    3. *Release notes & compatibility guidance:*
>
>
>    - Is there a recommended way to identify *function-level behavior
>       changes* between minor versions (beyond high-level release notes)?
>       - Are there guarantees or best-practice guidance around backward
>       compatibility expectations for PostGIS patch releases?
>
>
>    4. *Operational best practices:*
>
>
>    - Do you recommend pinning PostGIS patch versions in production where
>       possible, or validating only specific functions we rely on most during
>       upgrades?
>
> Any guidance you can share will help us reduce risk and plan upgrades more
> confidently.
>
> Thank you for your time and for all the work you do on PostGIS.
>
> Best regards,
> Bharath
> PostgreSQL Database Engineer
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20260121/835b3e09/attachment.htm>