[postgis-devel] In Place Upgrade

[Regina Obe]

We just need to fix the view.  I think you can copy the definition from 2.5 and backport to 2.4.

 

Looks like the new function pg_get_constraintdef we are using has existed at least since 9.2 so we should be okay with 2.4 fixing

 

https://www.postgresql.org/docs/9.2/functions-info.html#FUNCTIONS-INFO-CATALOG-TABLE

 

 

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

 

 





On Sep 24, 2019, at 9:58 AM, rmrodriguez at carto.com <mailto:rmrodriguez at carto.com>  wrote:

 

Already at 2.5.3…
postgis25_11-2.5.3-3.rhel7.x86_64


That's the binary, are the scripts installed in the database at 2.5.3 too?

 

Yes, this isn’t a production system, this is a blank (with one spatial table) database created today just to test upgrading against packages.









What would fixing 2.4 entail? Is there a ticket I can use to track this down? I think it’s worthwhile, probably.


It was done for 3 and 2.5 in https://trac.osgeo.org/postgis/ticket/4231

 

Thanks,

 

P







-- 
Raúl Marín Rodríguez
carto.com <http://carto.com> 
_______________________________________________
postgis-devel mailing list
postgis-devel at lists.osgeo.org <mailto:postgis-devel at lists.osgeo.org> 
https://lists.osgeo.org/mailman/listinfo/postgis-devel

 

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