From devrim at gunduz.org  Tue Jul  2 07:52:06 2024
From: devrim at gunduz.org (Devrim =?ISO-8859-1?Q?G=FCnd=FCz?=)
Date: Tue, 02 Jul 2024 17:52:06 +0300
Subject: PostgreSQL 17 support
In-Reply-To: <000c01dac8cd$4512ecd0$cf38c670$@pcorp.us>
References: <83a6cfa94e2f9d07f8e81ae3b7246dd1ef110630.camel@gunduz.org>
 <CACowWR1jS7A_HpRgEhZC8ZbBMYfCpKk8CzLCke=E4JVQYuCxLg@mail.gmail.com>
 <000c01dac8cd$4512ecd0$cf38c670$@pcorp.us>
Message-ID: <81d84830d8c77fa636b57d1211d7cd2140d4ce2e.camel@gunduz.org>

Hi

On Thu, 2024-06-27 at 16:04 -0400, Regina Obe wrote:
> 
> How do we feel about pushing out a PostGIS 3.5.0beta1 so we have a
> tagged build for PG17 to work against.

That would be great. Some people are already demanding for a PG17
compatible release.

> Or do we feel we won't be able to release 3.5.0 in time for PG17 in
> which case we need to backport changes to 3.4 and do another 3.4
> release.

That needs to be done anyway, I think for smoother updates.

Regards,

-- 
Devrim G?nd?z
Open Source Solution Architect, PostgreSQL Major Contributor
Twitter: @DevrimGunduz , @DevrimGunduzTR
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 858 bytes
Desc: This is a digitally signed message part
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20240702/29c08ae5/attachment.sig>

From lr at pcorp.us  Tue Jul  2 10:34:00 2024
From: lr at pcorp.us (Regina Obe)
Date: Tue, 2 Jul 2024 13:34:00 -0400
Subject: PostgreSQL 17 support
In-Reply-To: <81d84830d8c77fa636b57d1211d7cd2140d4ce2e.camel@gunduz.org>
References: <83a6cfa94e2f9d07f8e81ae3b7246dd1ef110630.camel@gunduz.org>	
 <CACowWR1jS7A_HpRgEhZC8ZbBMYfCpKk8CzLCke=E4JVQYuCxLg@mail.gmail.com>	
 <000c01dac8cd$4512ecd0$cf38c670$@pcorp.us>
 <81d84830d8c77fa636b57d1211d7cd2140d4ce2e.camel@gunduz.org>
Message-ID: <004501dacca6$06cbfc00$1463f400$@pcorp.us>

> > Or do we feel we won't be able to release 3.5.0 in time for PG17 in
> > which case we need to backport changes to 3.4 and do another 3.4
> > release.
> 
> That needs to be done anyway, I think for smoother updates.
> 
> Regards,
> 
> --
> Devrim G?nd?z
> Open Source Solution Architect, PostgreSQL Major Contributor
> Twitter: @DevrimGunduz , @DevrimGunduzTR

Why does it need to be done for smoother upgrades? 
Now that we got rid of the minor, people are better off just installing one version in PG17
And the dependencies between 3.4 and 3.5 aren't that different.

In the past the issue with upgrades would have been postgis-3.4.so vs. postgis-3.5.so  prevented clean pg_upgrade
But now they are both called postgis-3.so that should no longer be an issue.

Please let me know if I am missing something here.

Thanks,
Regina