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. I have only just discovered the following documentation: https://postgis.net/documentation/tips/tip-upgrading-raster-from-2-3/ 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. Q2: Should I still run postgis_full_version() - is this function a benign query, unlike postgis_extensions_upgrade() ? Thanks, Andrew On Tue, 25 Jun 2024 at 08:08, Sandro Santilli <s...@kbt.io> wrote: > Hi Andrew, replies inline > > On Mon, Jun 24, 2024 at 05:38:50PM +0100, Andrew Hardy wrote: > > > We noticed some odd failures executing a SELECT on a table with a point > > type column. The error was: 'could not access file > "$libdir/postgis-2.5": > > No such file or directory' . > > This means you have some left-over old PostGIS functions in your > database, so the upgrade was not complete. What does the following > query return ? > > SELECT postgis_full_version() > > --strk; >
