[postgis-devel] In Place Upgrade

[Regina Obe]

We have to provide a patch for 2.5 or below for it to work.

Though I thought we did that already.  Which postgis 2.5 are you upgrading from?

 

Have you tried doing 

 

ALTER EXTENSION postgis UPDATE;   -- on the old cluster (to bring it up to latest 2.5.3)

Then do the pg_upgrade?

 

The issue is when pg_upgrade does it’s upgrade it remember does this

 

1)      Creates a blank extension with nothing in it for PostGIS

2)      Then it goes thru the process of loading the extension functions, views etc AS IT EXISTED IN THE INSTALL (so it’s not using any PostGIS packaged scripts for that)

 

So since prior to our fix for 2.5 to work for 12, an old PostGIS 2.5 will not be compatible with 12 and thus can not be upgraded without first bringing it up to the latest micro (or at least micro since our fix).

 

That said I don’t think we back fixed 2.4 (or maybe we did).  Probably need to do at leat that much.

 

From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On Behalf Of Paul Ramsey
Sent: Tuesday, September 24, 2019 12:24 PM
To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>
Subject: [postgis-devel] In Place Upgrade

 

Anyone done an in-place upgrade from 11/2.5 to 12/3?

I'm working through one w/ the PGDG packages, found a couple bugs already, which are fixable in the packages, but just hit one that looks fatal on our side... at the end of pg_upgrade, we hit this one:

 

pg_restore: from TOC entry 214; 1259 18025 VIEW geometry_columns postgres
pg_restore: error: could not execute query: ERROR:  column s.consrc does not exist
LINE 28:             "replace"("split_part"("s"."consrc", ''''::"text...
                                            ^
HINT:  Perhaps you meant to reference the column "s.conkey" or the column "s.conbin".
Command was: 
-- For binary upgrade, must preserve pg_type oid
SELECT pg_catalog.binary_upgrade_set_next_pg_type_oid('18027'::pg_catalog.oid);

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20190924/4ab3bb3f/attachment.html>