[postgis-tickets] [PostGIS] #5194: SELECT postgis_extensions_upgrade() fails with pgextwlist

[PostGIS]

#5194: SELECT postgis_extensions_upgrade() fails with pgextwlist
------------------------------------+---------------------------
  Reporter:  robe                   |      Owner:  strk
      Type:  defect                 |     Status:  new
  Priority:  blocker                |  Milestone:  PostGIS 3.3.0
 Component:  build/upgrade/install  |    Version:  master
Resolution:                         |   Keywords:
------------------------------------+---------------------------
Comment (by robe):

 Replying to [comment:8 strk]:
 > I'm working on an alternative setup in which rather than messing the
 catalog tables to set our version to 'ANY' we install 0-bytes upgrade
 paths from any supported version to `ANY`, which does the SAME thing as
 the catalog update but using `ALTER EXTENSION UPDATE` instead of `UPDATE
 pg_extension`. It will still be good to try the direct catalog update in
 case those `<version>--ANY` upgrade files are missing for any reason
 (package managers end up dropping them or users want to avoid having all
 those files around). The work in progress is in an `upgrade-paths` branch
 in official repository

 Doesn't that still suffer from the issue of, if a user uninstalls a
 version before they upgrade, they are missing that

 <my current version>--ANY.sql

 script and since the new install won't provide that, they are still stuck?
 or is that where your make target comes into play, to install these
 missing files?
-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5194#comment:9>
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.