[postgis-tickets] [PostGIS] #3821: Don't drop st_union when updating postgis extension to 2.4

[PostGIS]

#3821: Don't drop st_union when updating postgis extension to 2.4
--------------------------+---------------------------
  Reporter:  nextstopsun  |      Owner:  robe
      Type:  defect       |     Status:  new
  Priority:  medium       |  Milestone:  PostGIS 2.5.0
 Component:  postgis      |    Version:  2.3.x
Resolution:               |   Keywords:
--------------------------+---------------------------

Comment (by robe):

 That works for me strk:

 When I do this from psql


 {{{
 \df+ ST_Union
 }}}

 it toggles to safe and setting it to 'u' switches it to unsafe.

 Now is it worthwhile to make an exception for ST_Union that it's used
 enough in views that we should just do the unholy and update the system
 catalog just for this agg function for PostgreSQL 9.6+ users upgrading to
 2.4.

 and take out the changed flag on it or should we just advice folks steps
 to take to upgrade if they run into the issue?

 nextstopsun -- what do you think are our instructions okay for you to
 follow

 1) remove the:

 {{{
 OR (
       204 = version_from_num AND version_from_isdev
     )
 }}}

 2) Do the update thing that strk mentioned -- this will work too:


 {{{
 UPDATE pg_proc SET proparallel = 's'
 WHERE oid = 'st_union(geometry)'::regprocedure;
 }}}

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