[postgis-tickets] [PostGIS] #3706: Use of deprecated function
PostGIS
trac at osgeo.org
Fri Dec 22 01:32:30 PST 2017
#3706: Use of deprecated function
--------------------------+---------------------------
Reporter: postgispaul | Owner: robe
Type: defect | Status: closed
Priority: high | Milestone: PostGIS 2.3.3
Component: postgis | Version: 2.3.x
Resolution: worksforme | Keywords:
--------------------------+---------------------------
Comment (by strk):
Ah yes, now I read the actual ticket.
Ok, the upgrade script will only update that aggregate IFF upgrading from
version 2.3.0 or lower, or if upgrading between 2.3.0-dev versions.
How you ended up in 2.3.2 with no upgrade I don't know, but I know there
are a lot of other things that would not upgrade anymore if they didn't
upgrade when it was time for it.
Maybe you could try, as an hack, to _pretend_ your installed postgis
version is < 2.3.0 buy overriding the `postgis_scripts_installed`
function. You'd do something like this:
{{{
BEGIN; -- do in a transaction, to rollback on failure
CREATE OR REPLACE FUNCTION postgis_scripts_installed() RETURNS text
AS $$ SELECT '2.3.0'::text || ' faked (real version is 2.4.2 r16113)' AS
version $$
LANGUAGE 'sql' IMMUTABLE;
}}}
Then you can check postgis_full_version(), just for fun, and then cross
your fingers and proceed to:
{{{
ALTER EXTENSION postgis UPDATE to 2.4.2next;
}}}
If everything went smooth you can then update again to 2.4.2 and finally
commit, otherwise
let us know what goes wrong.
--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/3706#comment:9>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.
More information about the postgis-tickets
mailing list