public inbox for [email protected]  
help / color / mirror / Atom feed
From: Justin Pryzby <[email protected]>
To: Devrim Gündüz <[email protected]>
Cc: [email protected]
Cc: Paul Ramsey <[email protected]>
Subject: Re: postgis for beta releases
Date: Sat, 12 Sep 2020 16:56:06 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

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 <[email protected]>
|Date:   Fri Oct 4 18:25:46 2019 +0000
|    Restore ST_Union() aggregate signature and re-work...

-- 
Justin





view thread (52+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: postgis for beta releases
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox