Inquiry on planned PostGIS releases and minor-versio n behavior (now–Feb 28)

--00000000000063f8ca0648ea34ec
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hello PostGIS Team,

I=E2=80=99m a PostgreSQL Database Engineer managing production PostgreSQL/P=
ostGIS
workloads on AWS RDS/Aurora.

We are planning a PostgreSQL *minor upgrade* (PostgreSQL 16.6 =E2=86=92 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 =E2=86=92 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 durin=
g
      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

--00000000000063f8ca0648ea34ec
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><p class=3D"gmail-isSelectedEnd">Hello PostGIS Team,<=
/p><p class=3D"gmail-isSelectedEnd">I=E2=80=99m a PostgreSQL Database Engin=
eer managing production PostgreSQL/PostGIS workloads on AWS RDS/Aurora.</p>=
<p class=3D"gmail-isSelectedEnd">We are planning a PostgreSQL <strong>minor=
 upgrade</strong> (PostgreSQL 16.6 =E2=86=92 16.11) in the near term. In ou=
r environment, past <strong>PostGIS minor/patch releases</strong> have occa=
sionally caused operational issues due to changes in function behavior, eve=
n when PostgreSQL itself was a minor upgrade. Because AWS may bundle a newe=
r PostGIS minor version along with a PostgreSQL minor upgrade, we want to p=
lan and execute testing and production rollout as close together as possibl=
e.</p><p class=3D"gmail-isSelectedEnd">To help us plan safely, I wanted to =
ask:</p><ol start=3D"1"><li><p class=3D"gmail-isSelectedEnd"><strong>Are th=
ere any planned PostGIS releases (minor or patch) between now and February =
28?</strong></p><ul><li><p class=3D"gmail-isSelectedEnd">If yes, which vers=
ions are anticipated?</p></li><li><p class=3D"gmail-isSelectedEnd">If not, =
when is the next postgis version release anticipated?</p></li></ul></li><li=
><p class=3D"gmail-isSelectedEnd"><strong>For PostGIS minor/patch releases =
(e.g., 3.6.x =E2=86=92 3.6.y):</strong></p><ul><li><p class=3D"gmail-isSele=
ctedEnd">Are changes strictly bug fixes, or can they include behavioral cha=
nges to existing functions?</p></li><li><p class=3D"gmail-isSelectedEnd">Ar=
e there specific classes of functions (geometry processing, topology, raste=
r, etc.) where behavior changes are more likely?</p></li></ul></li><li><p c=
lass=3D"gmail-isSelectedEnd"><strong>Release notes &amp; compatibility guid=
ance:</strong></p><ul><li><p class=3D"gmail-isSelectedEnd">Is there a recom=
mended way to identify <em>function-level behavior changes</em> between min=
or versions (beyond high-level release notes)?</p></li><li><p class=3D"gmai=
l-isSelectedEnd">Are there guarantees or best-practice guidance around back=
ward compatibility expectations for PostGIS patch releases?</p></li></ul></=
li><li><p class=3D"gmail-isSelectedEnd"><strong>Operational best practices:=
</strong></p><ul><li><p class=3D"gmail-isSelectedEnd">Do you recommend pinn=
ing PostGIS patch versions in production where possible, or validating only=
 specific functions we rely on most during upgrades?</p></li></ul></li></ol=
><p class=3D"gmail-isSelectedEnd">Any guidance you can share will help us r=
educe risk and plan upgrades more confidently.</p><p class=3D"gmail-isSelec=
tedEnd">Thank you for your time and for all the work you do on PostGIS.</p>=
<p>Best regards,<br>Bharath<br>PostgreSQL Database Engineer</p></div></div>

--00000000000063f8ca0648ea34ec--