[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:  closed
  Priority:  medium       |  Milestone:  PostGIS 2.4.0
 Component:  postgis      |    Version:  2.3.x
Resolution:  fixed        |   Keywords:
--------------------------+---------------------------

Comment (by dmkaplan2000):

 Replying to [comment:11 robe]:
 Hi,

 I know this has been closed for a while, but I am running into this
 problem upgrading from Postgis 2.4.3 to Postgis 2.5.2 on a Postgresql 10
 cluster on Ubuntu. I have desperately been trying to implement your
 solution of simply not dropping the ST_Union(geometry) aggregate, but I am
 obviously not editing the correct script as it has been having no effect.
 Would you mind indicating the correct file to edit? I have tried editing:

 /usr/share/postgresql/10/extension/postgis--ANY--2.5.2.sql
 /usr/share/postgresql/10/contrib/postgis-2.5/postgis_upgrade_for_extension.sql

 as well as several other similar file, but nothing seems to happen.

 Thanks!

 > Sadly I'm afraid since we don't keep track of changes within dev, going
 from PostGIS 2.4.0dev to PostGIS 2.4.0devnext for example will always try
 to drop and recreate the aggs.  Fussing with sys catalogs is beginning to
 feel more appealing to me now.
 >
 > What you could do for now if you really don't want to drop and recreate
 the aggs (or you just need to do it for ST_Union) , is  in the extension
 scripts -- e.g. postgis--2.4.0devnext--2.4.0dev.sql
 >
 > where it has
 >
 >
 > {{{
 > OR (
 >       204 = version_from_num AND version_from_isdev
 >     )
 > }}}
 >
 >  Wipe that out and it won't force drop and recreate aggs.  Again you can
 maybe just do it for ST_Union since I think ST_ASMVT has some aggs and
 those changes you might want to do.
 >
 > I have to lookup the sys catalogs but I think there is a way to directly
 update the sys catalogs to set the parallel safe bit on by directly
 updating the catalogs.
 >
 >
 >
 >

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