[postgis-tickets] [PostGIS] #5237: postgis_extensions_upgrade fails with ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification

[PostGIS]

#5237: postgis_extensions_upgrade fails with ERROR: there is no unique or
exclusion constraint matching the ON CONFLICT specification
----------------------+---------------------------
  Reporter:  robe     |      Owner:  pramsey
      Type:  defect   |     Status:  closed
  Priority:  medium   |  Milestone:  PostGIS 3.3.2
 Component:  postgis  |    Version:  3.3.x
Resolution:  wontfix  |   Keywords:
----------------------+---------------------------
Comment (by strk):

 I suspect the primary key was removed when going from 1.x to 2.x which is
 when we restricted the allowed range of SRID values. In that occasion the
 postgis_restore.pl script made an effort of MOVING out-of-range SRID
 values within the valid range, but doing so might have introduced a
 conflict (same SRID / different other values) so in order not to still
 allow restore it dropped the constraint, loaded the data and then tried to
 re-add the constraint. Maybe in your case re-adding the constraint failed.

 Is your problem solved by now ? Were you able to re-add the primary key ?
 Did you find conflicts ?
-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5237#comment:12>
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.