Date: Sat, 12 Sep 2020 16:56:06 -0500
From: Justin Pryzby <pryzby@telsasoft.com>
To: Devrim =?iso-8859-1?B?R/xuZPx6?= <devrim@gunduz.org>
Cc: pgsql-pkg-yum@postgresql.org, Paul Ramsey <pramsey@cleverelephant.ca>
Subject: Re: postgis for beta releases
Message-ID: <20200912215606.GR18552@telsasoft.com>
References: <20200710200430.GO26220@telsasoft.com>
 <7b35ba70ab939133932404dc7e617e042f63dede.camel@gunduz.org>
 <20200721181639.GK5748@telsasoft.com>
 <eb80ab3e500e87959942835b26f585b5beaceed9.camel@gunduz.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <eb80ab3e500e87959942835b26f585b5beaceed9.camel@gunduz.org>
User-Agent: Mutt/1.9.4 (2018-02-28)
Precedence: bulk

On Tue, Jul 28, 2020 at 11:14:43AM +0100, Devrim Gündüz wrote:
> On Tue, 2020-07-21 at 13:16 -0500, Justin Pryzby wrote:
> > As I mentioned, I think postgis30 should *also* be built for v13, and
> > postgis31 should *maybe* be built for v12:
> 
> Pushing them to v11 and v12 *testing* repos in an hour or so.

Note, I still suggest that postgis30 and postgis31 should *both* be built for
postgres13 and (at least) postgres12.

I've done a couple test upgrades from pg12 to 13, some using pg_dump/restore,
some using pg_upgrade.  In both cases, I first had to do:

|DROP AGGREGATE st_union(geometry);
|DROP FUNCTION pgis_geometry_union_transfn;

I guess postgis30 and 31 are "compatible enough" that I was able to restore a
postgis30 DB into a DB with only postgis31 available.

Normally, I'd have to do a "rolling upgrade", either:
(pg12+gis30) => (pg12+gis31) => (pg13+gis31), or:
(pg12+gis30) => (pg13+gis30) => (pg13+gis31).

I guess this is related to postgis commit 75a044c61:

|Author: Paul Ramsey <pramsey@cleverelephant.ca>
|Date:   Fri Oct 4 18:25:46 2019 +0000
|    Restore ST_Union() aggregate signature and re-work...

-- 
Justin