[postgis-tickets] [PostGIS] #4334: Can't upgrade with a view based on ST_AsMVTGeom

[PostGIS]

#4334: Can't upgrade with a view based on ST_AsMVTGeom
------------------------------------+---------------------------
  Reporter:  Algunenano             |      Owner:  strk
      Type:  defect                 |     Status:  new
  Priority:  high                   |  Milestone:  PostGIS 2.4.7
 Component:  build/upgrade/install  |    Version:  2.4.x
Resolution:                         |   Keywords:
------------------------------------+---------------------------

Comment (by strk):

 > The idea is that you pass the complete signature of the old function and
 > it will only try to drop it if it matches the one installed, so passing
 > the new signature isn't necessary.

 You mean if it does NOT match the one installed, right ?
 The new signature isn't visible at upgrade time, because we
 drop the old one _before_ the new one is installed.
 So, to recap: the OLD (current) signature is known, while
 the NEW (to be installed) isn't.

 > Automating this for all functions looks really complex, but I can
 > probably hook the view tests I did above.

 A step in that direction would be good, even if it is only a
 manually edited sql file creating those constraining views.
 We can think about automating the generation of those view
 in a second step (I guess it would fail for some upgrade paths
 in that we didn't always restrict changes to compatible ones).

 Having a test in advance is also good to _prove_ the usefulness
 of the code change...

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