[postgis-tickets] [PostGIS] #5046: Old postgis library needed to upgrade

[PostGIS]

#5046: Old postgis library needed to upgrade
------------------------------------+---------------------------
  Reporter:  robe                   |      Owner:  strk
      Type:  defect                 |     Status:  new
  Priority:  medium                 |  Milestone:  PostGIS 3.2.1
 Component:  build/upgrade/install  |    Version:  3.2.x
Resolution:                         |   Keywords:
------------------------------------+---------------------------

Comment (by strk):

 I guess the special thing about those functions is that they have a
 DEFAULT value expressed in a canonical text for type GEOMETRY:
 {{{
 CREATE OR REPLACE FUNCTION ST_Square(size float8, cell_i integer, cell_j
 integer, origin geometry DEFAULT 'POINT(0 0)')
 CREATE OR REPLACE FUNCTION ST_Square(size float8, cell_i integer, cell_j
 integer, origin geometry DEFAULT 'POINT(0 0)')
 CREATE OR REPLACE FUNCTION ST_Angle(pt1 geometry, pt2 geometry, pt3
 geometry, pt4 geometry default 'POINT EMPTY'::geometry)
 CREATE OR REPLACE FUNCTION ST_TileEnvelope(zoom integer, x integer, y
 integer, bounds geometry DEFAULT 'SRID=3857;LINESTRING(-20037508.342789244
 -20037508.342789244, 20037508.342789244 20037508.342789244)'::geometry,
 margin float8 DEFAULT 0.0)
 }}}

 BTW, ST_TileEnvelope default looks weird to me (what's that?)

 Anyway, it looks like {{{ pg_get_function_arguments }}} (which is used by
 {{{ _postgis_drop_function_if_needed }}}) chokes when the default value of
 a geometry is given.

 I guess this is because some function associated with the GEOMETRY type is
 invoked (typmod_in? input?)

-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5046#comment:5>
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.