RE: Inquiry on planned PostGIS r eleases and minor-version behavi or (now–Feb 28)

"Regina Obe" <[email protected]> Wed, 21 Jan 2026 14:56:03 -0500
Newsgroups gmane.comp.gis.postgis
Message-ID <[email protected]> 
This is a multipart message in MIME format.

------=_NextPart_000_003B_01DC8AE6.10DD4500
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

As Paul mentioned, we don=E2=80=99t have tentative date plans.   We =
release when we feel there are enough bug fixes in the list to make it =
worthwhile or if enough time has passed.

At the moment we generally don=E2=80=99t make a decision to release =
until about a week before we release.

=20

Not sure what you mean by GEOS/PROJ changes.  Those are separate =
projects from PostGIS.  PostGIS just relies on them.

=20

=20

=20

From: Bharath Tadikonda <[email protected]>=20
Sent: Wednesday, January 21, 2026 2:38 PM
To: Regina Obe <[email protected]>
Cc: [email protected]
Subject: Re: Inquiry on planned PostGIS releases and minor-version =
behavior (now=E2=80=93Feb 28)

=20

Hi Regina,

=20

"and yes we most likely will do a micro release before February 28"=20

=20

Could you please let us know if there is a tentative date planned for =
this micro release? Additionally, will this release include any changes =
to GEOS or PROJ?

=20

On Wed, Jan 21, 2026 at 2:09=E2=80=AFPM Regina Obe <[email protected] =
<mailto:[email protected]> > wrote:

Bharath,

=20

The best advice I can give is to look at the upcoming NEWS items

=20

https://gitea.osgeo.org/postgis/postgis/src/branch/stable-3.6/NEWS

=20

and yes we most likely will do a micro release before February 28

=20

=20

From: Bharath Tadikonda <[email protected] =
<mailto:[email protected]> >=20
Sent: Wednesday, January 21, 2026 1:36 PM
To: [email protected] <mailto:[email protected]> =

Subject: Inquiry on planned PostGIS releases and minor-version behavior =
(now=E2=80=93Feb 28)

=20

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 =
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 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


------=_NextPart_000_003B_01DC8AE6.10DD4500
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 15 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Aptos;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	font-size:12.0pt;
	font-family:"Aptos",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
p.m2462710951653754678gmail-isselectedend, =
li.m2462710951653754678gmail-isselectedend, =
div.m2462710951653754678gmail-isselectedend
	{mso-style-name:m_2462710951653754678gmail-isselectedend;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Aptos",sans-serif;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Aptos",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:278224030;
	mso-list-template-ids:-445458084;}
@list l0:level1
	{mso-level-start-at:4;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l1
	{mso-list-id:416904423;
	mso-list-template-ids:1071397804;}
@list l1:level1
	{mso-level-start-at:4;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2
	{mso-list-id:550388360;
	mso-list-template-ids:1118966428;}
@list l2:level1
	{mso-level-start-at:2;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l3
	{mso-list-id:614140703;
	mso-list-template-ids:-971051534;}
@list l4
	{mso-list-id:999649719;
	mso-list-template-ids:-2034871120;}
@list l4:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l5
	{mso-list-id:1379159900;
	mso-list-template-ids:-1625134504;}
@list l5:level1
	{mso-level-start-at:3;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l6
	{mso-list-id:1606690786;
	mso-list-template-ids:1693355836;}
@list l6:level1
	{mso-level-start-at:2;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l7
	{mso-list-id:2039311588;
	mso-list-template-ids:-2111558698;}
@list l7:level1
	{mso-level-start-at:3;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l7:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style></head><body lang=3DEN-US link=3Dblue vlink=3Dpurple =
style=3D'word-wrap:break-word'><div class=3DWordSection1><p =
class=3DMsoNormal>As Paul mentioned, we don=E2=80=99t have tentative =
date plans.=C2=A0 =C2=A0We release when we feel there are enough bug =
fixes in the list to make it worthwhile or if enough time has =
passed.<o:p></o:p></p><p class=3DMsoNormal>At the moment we generally =
don=E2=80=99t make a decision to release until about a week before we =
release.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Not sure what you mean by GEOS/PROJ changes.=C2=A0 =
Those are separate projects from PostGIS.=C2=A0 PostGIS just relies on =
them.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #E1E1E1 =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span><=
/b><span style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif'> =
Bharath Tadikonda &lt;[email protected]&gt; <br><b>Sent:</b> =
Wednesday, January 21, 2026 2:38 PM<br><b>To:</b> Regina Obe =
&lt;[email protected]&gt;<br><b>Cc:</b> =
[email protected]<br><b>Subject:</b> Re: Inquiry on planned =
PostGIS releases and minor-version behavior (now=E2=80=93Feb =
28)<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p class=3DMsoNormal>Hi =
Regina,<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p =
class=3DMsoNormal><i><span style=3D'color:black'>&quot;and yes we most =
likely will do a micro release before February =
28&quot;&nbsp;</span></i><o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p>Could you please =
let us know if there is a tentative date planned for this micro release? =
Additionally, will this release include any changes to <strong><span =
style=3D'font-family:"Aptos",sans-serif'>GEOS</span></strong> or =
<strong><span =
style=3D'font-family:"Aptos",sans-serif'>PROJ</span></strong>?<o:p></o:p>=
</p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p =
class=3DMsoNormal>On Wed, Jan 21, 2026 at 2:09<span =
style=3D'font-family:"Arial",sans-serif'>=E2=80=AF</span>PM Regina Obe =
&lt;<a href=3D"mailto:[email protected]">[email protected]</a>&gt; =
wrote:<o:p></o:p></p></div><blockquote =
style=3D'border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in =
6.0pt;margin-left:4.8pt;margin-right:0in'><div><div><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Bharath,<o:p=
></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>The best =
advice I can give is to look at the upcoming NEWS items<o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><a =
href=3D"https://gitea.osgeo.org/postgis/postgis/src/branch/stable-3.6/NEW=
S" =
target=3D"_blank">https://gitea.osgeo.org/postgis/postgis/src/branch/stab=
le-3.6/NEWS</a><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>and yes we =
most likely will do a micro release before February 28<o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p><div style=3D'border:none;border-left:solid blue =
1.5pt;padding:0in 0in 0in 4.0pt'><div><div =
style=3D'border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span =
style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span><=
/b><span style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif'> =
Bharath Tadikonda &lt;<a href=3D"mailto:[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">[email protected]</a><br><b>Subject:</b> =
Inquiry on planned PostGIS releases and minor-version behavior =
(now=E2=80=93Feb 28)</span><o:p></o:p></p></div></div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p><div><div><p =
class=3Dm2462710951653754678gmail-isselectedend>Hello PostGIS =
Team,<o:p></o:p></p><p =
class=3Dm2462710951653754678gmail-isselectedend>I=E2=80=99m a PostgreSQL =
Database Engineer managing production PostgreSQL/PostGIS workloads on =
AWS RDS/Aurora.<o:p></o:p></p><p =
class=3Dm2462710951653754678gmail-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</span></strong> 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.<o:p></o:p></p><p =
class=3Dm2462710951653754678gmail-isselectedend>To help us plan safely, =
I wanted to ask:<o:p></o:p></p><ol start=3D1 type=3D1><li =
class=3Dm2462710951653754678gmail-isselectedend style=3D'mso-list:l3 =
level1 lfo1'><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><o:p></o:p></li></ol><ol start=3D1 =
type=3D1><ul type=3Dcircle><li =
class=3Dm2462710951653754678gmail-isselectedend style=3D'mso-list:l4 =
level2 lfo2'>If yes, which versions are anticipated?<o:p></o:p></li><li =
class=3Dm2462710951653754678gmail-isselectedend style=3D'mso-list:l4 =
level2 lfo2'>If not, when is the next postgis version release =
anticipated?<o:p></o:p></li></ul></ol><ol start=3D2 type=3D1><li =
class=3Dm2462710951653754678gmail-isselectedend style=3D'mso-list:l6 =
level1 lfo3'><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><o:p></o:p></li></ol><ol start=3D2 type=3D1><ul =
type=3Dcircle><li class=3Dm2462710951653754678gmail-isselectedend =
style=3D'mso-list:l2 level2 lfo4'>Are changes strictly bug fixes, or can =
they include behavioral changes to existing =
functions?<o:p></o:p></li><li =
class=3Dm2462710951653754678gmail-isselectedend style=3D'mso-list:l2 =
level2 lfo4'>Are there specific classes of functions (geometry =
processing, topology, raster, etc.) where behavior changes are more =
likely?<o:p></o:p></li></ul></ol><ol start=3D3 type=3D1><li =
class=3Dm2462710951653754678gmail-isselectedend style=3D'mso-list:l5 =
level1 lfo5'><strong><span =
style=3D'font-family:"Aptos",sans-serif'>Release notes &amp; =
compatibility guidance:</span></strong><o:p></o:p></li></ol><ol =
start=3D3 type=3D1><ul type=3Dcircle><li =
class=3Dm2462710951653754678gmail-isselectedend style=3D'mso-list:l7 =
level2 lfo6'>Is there a recommended way to identify <em><span =
style=3D'font-family:"Aptos",sans-serif'>function-level behavior =
changes</span></em> between minor versions (beyond high-level release =
notes)?<o:p></o:p></li><li =
class=3Dm2462710951653754678gmail-isselectedend style=3D'mso-list:l7 =
level2 lfo6'>Are there guarantees or best-practice guidance around =
backward compatibility expectations for PostGIS patch =
releases?<o:p></o:p></li></ul></ol><ol start=3D4 type=3D1><li =
class=3Dm2462710951653754678gmail-isselectedend style=3D'mso-list:l1 =
level1 lfo7'><strong><span =
style=3D'font-family:"Aptos",sans-serif'>Operational best =
practices:</span></strong><o:p></o:p></li></ol><ol start=3D4 =
type=3D1><ul type=3Dcircle><li =
class=3Dm2462710951653754678gmail-isselectedend style=3D'mso-list:l0 =
level2 lfo8'>Do you recommend pinning PostGIS patch versions in =
production where possible, or validating only specific functions we rely =
on most during upgrades?<o:p></o:p></li></ul></ol><p =
class=3Dm2462710951653754678gmail-isselectedend>Any guidance you can =
share will help us reduce risk and plan upgrades more =
confidently.<o:p></o:p></p><p =
class=3Dm2462710951653754678gmail-isselectedend>Thank you for your time =
and for all the work you do on PostGIS.<o:p></o:p></p><p>Best =
regards,<br>Bharath<br>PostgreSQL Database =
Engineer<o:p></o:p></p></div></div></div></div></div></div></blockquote><=
/div></div></div></body></html>
------=_NextPart_000_003B_01DC8AE6.10DD4500--