| From: | "Regina Obe" <lr(at)pcorp(dot)us> |
|---|---|
| To: | "'PostGIS Development Discussion'" <postgis-devel(at)lists(dot)osgeo(dot)org> |
| Cc: | "'PostgreSQL Developers'" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | RE: [postgis-devel] About EXTENSION from UNPACKAGED on PostgreSQL 13 |
| Date: | 2020-02-26 20:11:29 |
| Message-ID: | 002101d5ece0$eef571f0$cce055d0$@pcorp.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2020-02-26 20:40:02 | Re: proposal: schema variables |
| Previous Message | Andrew Dunstan | 2020-02-26 20:04:52 | Re: Resolving the python 2 -> python 3 mess |