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

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

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

On Wed, Jan 21, 2026 at 2:09=E2=80=AFPM Regina Obe <[email protected]> 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 <[email protected]>
> *Sent:* Wednesday, January 21, 2026 1:36 PM
> *To:* [email protected]
> *Subject:* Inquiry on planned PostGIS releases and minor-version behavior
> (now=E2=80=93Feb 28)
>
>
>
> Hello PostGIS Team,
>
> I=E2=80=99m a PostgreSQL Database Engineer managing production PostgreSQL=
/PostGIS
> workloads on AWS RDS/Aurora.
>
> We are planning a PostgreSQL *minor upgrade* (PostgreSQL 16.6 =E2=86=92 1=
6.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 ma=
y
> bundle a newer PostGIS minor version along with a PostgreSQL minor upgrad=
e,
> 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 dur=
ing
>       upgrades?
>
> Any guidance you can share will help us reduce risk and plan upgrades mor=
e
> confidently.
>
> Thank you for your time and for all the work you do on PostGIS.
>
> Best regards,
> Bharath
> PostgreSQL Database Engineer
>

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

<div dir=3D"ltr">

Thank you, Paul and Regina, for your responses. I really appreciate your ti=
me and the helpful information. I=E2=80=99ll review this on our side and wi=
ll reach out if we need any further clarification

</div><br><div class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr"=
 class=3D"gmail_attr">On Wed, Jan 21, 2026 at 2:09=E2=80=AFPM Regina Obe &l=
t;<a href=3D"mailto:[email protected]">[email protected]</a>&gt; wrote:<br></div><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1=
px solid rgb(204,204,204);padding-left:1ex"><div class=3D"msg24627109516537=
54678"><div lang=3D"EN-US" style=3D"overflow-wrap: break-word;"><div class=
=3D"m_2462710951653754678WordSection1"><p class=3D"MsoNormal">Bharath,<u></=
u><u></u></p><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p><p class=3D"Mso=
Normal">The best advice I can give is to look at the upcoming NEWS items<u>=
</u><u></u></p><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p><p class=3D"M=
soNormal"><a href=3D"https://gitea.osgeo.org/postgis/postgis/src/branch/sta=
ble-3.6/NEWS" target=3D"_blank">https://gitea.osgeo.org/postgis/postgis/src=
/branch/stable-3.6/NEWS</a><u></u><u></u></p><p class=3D"MsoNormal"><u></u>=
=C2=A0<u></u></p><p class=3D"MsoNormal">and yes we most likely will do a mi=
cro release before February 28<u></u><u></u></p><p class=3D"MsoNormal"><u><=
/u>=C2=A0<u></u></p><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p><div sty=
le=3D"border-top:none;border-right:none;border-bottom:none;border-left:1.5p=
t solid blue;padding:0in 0in 0in 4pt"><div><div style=3D"border-right:none;=
border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);p=
adding:3pt 0in 0in"><p class=3D"MsoNormal"><b><span style=3D"font-size:11pt=
;font-family:Calibri,sans-serif">From:</span></b><span style=3D"font-size:1=
1pt;font-family:Calibri,sans-serif"> Bharath Tadikonda &lt;<a href=3D"mailt=
o:[email protected]" target=3D"_blank">[email protected]<=
/a>&gt; <br><b>Sent:</b> Wednesday, January 21, 2026 1:36 PM<br><b>To:</b> =
<a href=3D"mailto:[email protected]" target=3D"_blank">postgis-=
[email protected]</a><br><b>Subject:</b> Inquiry on planned PostGIS rel=
eases and minor-version behavior (now=E2=80=93Feb 28)<u></u><u></u></span><=
/p></div></div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p><div><div><p =
class=3D"m_2462710951653754678gmail-isselectedend">Hello PostGIS Team,<u></=
u><u></u></p><p class=3D"m_2462710951653754678gmail-isselectedend">I=E2=80=
=99m a PostgreSQL Database Engineer managing production PostgreSQL/PostGIS =
workloads on AWS RDS/Aurora.<u></u><u></u></p><p class=3D"m_246271095165375=
4678gmail-isselectedend">We are planning a PostgreSQL <strong><span style=
=3D"font-family:Aptos,sans-serif">minor upgrade</span></strong> (PostgreSQL=
 16.6 =E2=86=92 16.11) in the near term. In our environment, past <strong><=
span style=3D"font-family:Aptos,sans-serif">PostGIS minor/patch releases</s=
pan></strong> have occasionally caused operational issues due to changes in=
 function behavior, even when PostgreSQL itself was a minor upgrade. Becaus=
e AWS may bundle a newer PostGIS minor version along with a PostgreSQL mino=
r upgrade, we want to plan and execute testing and production rollout as cl=
ose together as possible.<u></u><u></u></p><p class=3D"m_246271095165375467=
8gmail-isselectedend">To help us plan safely, I wanted to ask:<u></u><u></u=
></p><ol start=3D"1" type=3D"1"><li class=3D"m_2462710951653754678gmail-iss=
electedend"><strong><span style=3D"font-family:Aptos,sans-serif">Are there =
any planned PostGIS releases (minor or patch) between now and February 28?<=
/span></strong><u></u><u></u></li></ol><ol start=3D"1" type=3D"1"><ul type=
=3D"circle"><li class=3D"m_2462710951653754678gmail-isselectedend">If yes, =
which versions are anticipated?<u></u><u></u></li><li class=3D"m_2462710951=
653754678gmail-isselectedend">If not, when is the next postgis version rele=
ase anticipated?<u></u><u></u></li></ul></ol><ol start=3D"2" type=3D"1"><li=
 class=3D"m_2462710951653754678gmail-isselectedend"><strong><span style=3D"=
font-family:Aptos,sans-serif">For PostGIS minor/patch releases (e.g., 3.6.x=
 =E2=86=92 3.6.y):</span></strong><u></u><u></u></li></ol><ol start=3D"2" t=
ype=3D"1"><ul type=3D"circle"><li class=3D"m_2462710951653754678gmail-issel=
ectedend">Are changes strictly bug fixes, or can they include behavioral ch=
anges to existing functions?<u></u><u></u></li><li class=3D"m_2462710951653=
754678gmail-isselectedend">Are there specific classes of functions (geometr=
y processing, topology, raster, etc.) where behavior changes are more likel=
y?<u></u><u></u></li></ul></ol><ol start=3D"3" type=3D"1"><li class=3D"m_24=
62710951653754678gmail-isselectedend"><strong><span style=3D"font-family:Ap=
tos,sans-serif">Release notes &amp; compatibility guidance:</span></strong>=
<u></u><u></u></li></ol><ol start=3D"3" type=3D"1"><ul type=3D"circle"><li =
class=3D"m_2462710951653754678gmail-isselectedend">Is there a recommended w=
ay to identify <em><span style=3D"font-family:Aptos,sans-serif">function-le=
vel behavior changes</span></em> between minor versions (beyond high-level =
release notes)?<u></u><u></u></li><li class=3D"m_2462710951653754678gmail-i=
sselectedend">Are there guarantees or best-practice guidance around backwar=
d compatibility expectations for PostGIS patch releases?<u></u><u></u></li>=
</ul></ol><ol start=3D"4" type=3D"1"><li class=3D"m_2462710951653754678gmai=
l-isselectedend"><strong><span style=3D"font-family:Aptos,sans-serif">Opera=
tional best practices:</span></strong><u></u><u></u></li></ol><ol start=3D"=
4" type=3D"1"><ul type=3D"circle"><li class=3D"m_2462710951653754678gmail-i=
sselectedend">Do you recommend pinning PostGIS patch versions in production=
 where possible, or validating only specific functions we rely on most duri=
ng upgrades?<u></u><u></u></li></ul></ol><p class=3D"m_2462710951653754678g=
mail-isselectedend">Any guidance you can share will help us reduce risk and=
 plan upgrades more confidently.<u></u><u></u></p><p class=3D"m_24627109516=
53754678gmail-isselectedend">Thank you for your time and for all the work y=
ou do on PostGIS.<u></u><u></u></p><p>Best regards,<br>Bharath<br>PostgreSQ=
L Database Engineer<u></u><u></u></p></div></div></div></div></div></div></=
blockquote></div>

--000000000000c00e570648eac83d--