Update postgis in a replicated PostgreSQL 12 database now with postgis-3

[Sandro Santilli]

On Mon, Jul 01, 2024 at 04:37:37PM +0100, Andrew Hardy wrote:
> Thank you so much for your response, I appreciate it.
> 
> I omitted to mention that before I messaged I had tried to resolve this in
> the  pg_proc table and ran the following query:
> 
> UPDATE pg_proc SET probin = '$libdir/postgis-3' WHERE probin =
> '$libdir/rtpostgis-2.5';
> 
> This was probably a mistake (not least that postgis-3 is not the raster
> library) and I am wondering if this is resolvable.

Yes, it was a mistake.
Running this should fix it:

  SELECT postgis_extensions_upgrade();

> Q1: And I am wondering if the postgis_extensions_upgrade()  mentioned in
> the upgrade instructions assumes one is starting from a particular state
> and I need to get back there from my mistake above or if this upgrade
> function will resolve things whatever the state.

It tries its best to resolve things whatever the state, but I guess it
could fail, you'll tell us.

> Q2: Should I still run postgis_full_version() - is this function a
> benign query, unlike postgis_extensions_upgrade()  ?

Always run `postgis_full_version()` to tell what the state of the
database is.

--strk;
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20240807/314281ce/attachment.sig>