[postgis-tickets] [PostGIS] #5344: Restoring extension based topology dump fails resetting the topology sequence

[PostGIS]

#5344: Restoring extension based topology dump fails resetting the topology
sequence
-----------------------+---------------------------
  Reporter:  strk      |      Owner:  strk
      Type:  defect    |     Status:  new
  Priority:  medium    |  Milestone:  PostGIS 3.4.0
 Component:  topology  |    Version:  master
Resolution:            |   Keywords:
-----------------------+---------------------------
Comment (by robe):

 Replying to [comment:2 strk]:
 > I've pushed the fix of the bug, but I've seen that upgrading from a
 version of the extension PRIOR to the fix DOES NOT fix the database. That
 is, the pg_catalog.pg_extension_config_dump call does not end in the
 extension upgrade script.
 >
 > I suspect this is NOT just an issue with topology but also with all
 other extensions.
 >
 > Regina: do you have experience with this ? Is it ok to call
 pg_catalog.pg_extension_config_dump multiple times ? (idempotent?)

 Yes we used to have issue with postgis with the spatial_ref_sys dump that
 it would call for each upgrade and then the config table would explode.
 They fixed this issue a while ago, so should be safe to call for every
 ALTER EXTENSION update.  In fact I think we do that for spatial_ref_sys
-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5344#comment:4>
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.