| From: | Jeremy Schneider <schneider(at)ardentperf(dot)com> |
|---|---|
| To: | Slavcho Trnkovski <strnkovski(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: postgis after pg_upgrade |
| Date: | 2018-12-04 18:41:40 |
| Message-ID: | ebbc31f8-b29a-8efb-5516-ef9e774d9d2b@ardentperf.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 11/30/18 05:11, Slavcho Trnkovski wrote:
> I have postgresql 9.4 with postgis extension installed (latest version,
> 2.4.5). I upgraded postgresql from 9.4 to 9.6.
> After upgrading to 9.6 I get the following result
> from PostGIS_full_version()
> select PostGIS_full_version();
>
> ... (procs need upgrade for use with "96") ...
>
> Is there any way to resolve this besides recreating the extension?
If I'm reading the postgis docs correctly, this message specifically
means that you must do a full dump/reload of postgis-enabled databases.
http://postgis.net/docs/manual-2.4/postgis_installation.html#upgrading
> If you can't find the postgis_upgrade*.sql specific for upgrading
> your version you are using a version too early for a soft upgrade
> and need to do a HARD UPGRADE.
>
> The PostGIS_Full_Version function should inform you about the need
> to run this kind of upgrade using a "procs need upgrade" message.
>
> By HARD UPGRADE we mean full dump/reload of postgis-enabled
> databases.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martin Mueller | 2018-12-04 20:29:38 | simple division |
| Previous Message | Igor Neyman | 2018-12-04 16:09:09 | RE: How to watch for schema changes |