[postgis-tickets] [PostGIS] #4460: Problems migrating Postgis 2.1 to 2.4
PostGIS
trac at osgeo.org
Thu Jul 18 05:08:10 PDT 2019
#4460: Problems migrating Postgis 2.1 to 2.4
------------------------+---------------------------
Reporter: davidperez | Owner: pramsey
Type: defect | Status: new
Priority: high | Milestone: PostGIS 2.4.8
Component: postgis | Version: 2.4.x
Keywords: |
------------------------+---------------------------
We are using currntly Postgres 9.3 and Postgis 2.1.8, under CentOS 7.
we would like to migrate to Postgres 11 and Postgis 2.5.2.
Steps we follow:
- Compile Postgis 2.4.7 to Posgres 9.3
- Install it
- Migrate Postgis from 2.1.8 to 2.4.7 with ALTER EXTENSION postgis UPDATE
- It works ok but we receive this warning:
WARNING: 'postgis.backend' is already set and cannot be changed until
you reconnect
CONTEXT: sentencia SQL: «SELECT
postgis_lib_version()»
function PL/pgSQL postgis_major_version_check() in line 21 of SQL sentence
{code}
- Migrate with pg_upgrade from Postgres 9.3 with pg_upgrade. It works ok
Wiht the command:
psql \dx+
We see some functions are missing:
clase de operadores «brin_geography_inclusion_ops» para el método de
acceso «brin»
clase de operadores «brin_geometry_inclusion_ops_2d» para el método de
acceso «brin»
clase de operadores «brin_geometry_inclusion_ops_3d» para el método de
acceso «brin»
clase de operadores «brin_geometry_inclusion_ops_4d» para el método de
acceso «brin»
familia de operadores brin_geography_inclusion_ops para el método de
acceso brin
familia de operadores brin_geometry_inclusion_ops_2d para el método de
acceso brin
familia de operadores brin_geometry_inclusion_ops_3d para el método de
acceso brin
familia de operadores brin_geometry_inclusion_ops_4d para el método de
acceso brin
función contains_2d(box2df,box2df)
función contains_2d(box2df,geometry)
función contains_2d(geometry,box2df)
función geog_brin_inclusion_add_value(internal,internal,internal,internal)
función
geom2d_brin_inclusion_add_value(internal,internal,internal,internal)
función
geom3d_brin_inclusion_add_value(internal,internal,internal,internal)
función
geom4d_brin_inclusion_add_value(internal,internal,internal,internal)
función is_contained_2d(box2df,box2df)
función is_contained_2d(box2df,geometry)
función is_contained_2d(geometry,box2df)
función overlaps_2d(box2df,box2df)
función overlaps_2d(box2df,geometry)
función overlaps_2d(geometry,box2df)
función overlaps_geog(geography,gidx)
función overlaps_geog(gidx,geography)
función overlaps_geog(gidx,gidx)
función overlaps_nd(geometry,gidx)
función overlaps_nd(gidx,geometry)
función overlaps_nd(gidx,gidx)
operador ~(box2df,box2df)
operador @(box2df,box2df)
operador &&(box2df,box2df)
operador ~(box2df,geometry)
operador @(box2df,geometry)
operador &&(box2df,geometry)
operador &&(geography,gidx)
operador ~(geometry,box2df)
operador @(geometry,box2df)
operador &&(geometry,box2df)
operador &&&(geometry,gidx)
operador &&(gidx,geography)
operador &&&(gidx,geometry)
operador &&(gidx,gidx)
Another sympton is this:
select postgis_full_version() returns
2.4.7 r17330" PGSQL="93" (procs need upgrade for use with "110")
GEOS="3.7.1-CAP
I-1.11.1 27a5e771" PROJ="Rel. 4.9.3, 15 August 2016" GDAL="GDAL 1.11.4,
released 2016/01/2
5" LIBXML="2.9.1" LIBJSON="0.11" RASTER
If we do:
DROP EXTENSION POSTGIS
CREATE EXTENSION POSTGIS
then:
POSTGIS="2.4.7 r17330" PGSQL="110" GEOS="3.7.1-CAPI-1.11.1 27a5e771"
PROJ="Rel. 4.9.3, 15
August 2016" GDAL="GDAL 1.11.4, released 2016/01/25" LIBXML="2.9.1"
LIBJSON="0.11" RASTER
But we cannot do it in databases with geometric data.
Migration to 2.5.2 also fails:
https://gis.stackexchange.com/questions/327509/migration-in-postgresql-11
-from-postgis-2-4-to-2-5-fails
I think this is a bug in Postgis migration.
--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/4460>
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