[postgis-devel] About EXTENSION from UNPACKAGED on PostgreSQL 13

[Paul Ramsey]

> On Feb 26, 2020, at 1:12 PM, Bruce Rindahl <bruce.rindahl at gmail.com> wrote:
> 
> When ever I upgrade, I simply install the new version side by side on the same machine but on a different port.  Then I do:
> pg_restore -p 5432 mydbase | psql -p 5433 mydbase
> and see if anything throws an error.  If everything works, I test it for a while and then finally shut them down and swap ports in postgresql.conf 
> Will this avoid the issue?

Yes. Dump’n’restore workflows like this work fine. It’s in-place upgrades that are finnicky.
P

> 
> On Wed, Feb 26, 2020 at 12:11 PM Regina Obe <lr at pcorp.us> wrote:
> > Presumably 15 years out from the 1.x -> 2.x we can stop worrying about
> > bundling unpackaged postgis into an extension, and just recommend a hard
> > upgrade dump/restore to the hardy souls still running 1.x.
> > 
> > P.
> > 
> 
> We don't need to worry about 1.x cause 1.x can only do a hard upgrade to 2 or 3.  We never supported soft upgrade from 1.x
> Easy solution there is just to install postgis extension and do pg_restore/postgis_restore of your data.
> 
> So it's really just the 2.1 -> 3 that are of concern.
> I think now is a fine time to encourage everyone to upgrade to 3 if they can so they don't need to suffer any crazy solutions we come up with  :)
> 
> Turn this into a convenient emergency.
> 
> Thanks,
> Regina
> 
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-devel
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-devel