[PostGIS] #5983: Data corruption in topology.topoelement and topology.topogeometry after upgrade to 3.6.0

[PostGIS]

#5983: Data corruption in topology.topoelement and topology.topogeometry after
upgrade to 3.6.0
-----------------------+---------------------------
  Reporter:  packi     |      Owner:  robe
      Type:  defect    |     Status:  new
  Priority:  blocker   |  Milestone:  PostGIS 3.6.1
 Component:  topology  |    Version:  3.6.x
Resolution:            |   Keywords:
-----------------------+---------------------------
Comment (by robe):

 Replying to [comment:12 strk]:
 > I can't think of any 100% effective way to fix the corruption introduced
 by the upgrade to 3.6.0.
 >
 > I wouldn't know how we can tell which data was created BEFORE the
 catalog update and which data was created AFTER it, unless we can compare
 the transaction identifiers between the rows in the tables and the domain
 catalog row ?
 >
 > Or we could use some fuzzy logic to check if any data value would be
 invalid, and bet on that being caused by the corruption.
 >
 > Maybe we should retire 3.6.0 and make an announcement recommending
 anyone who already upgraded to get back to 3.5.x from backups, if they
 still can ...


 I'm suspecting very few people are using the bigint feature, so we might
 be able to fix simply by updating the catalog back to what it was.  Going
 to test that theory out.
-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5983#comment:13>
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.