[postgis-tickets] [PostGIS] #3429: upgrade from 2.1.3 to 2.3.0dev enters infinite loop

[PostGIS]

#3429: upgrade from 2.1.3 to 2.3.0dev enters infinite loop
------------------------------------+---------------------------
  Reporter:  strk                   |      Owner:  strk
      Type:  defect                 |     Status:  new
  Priority:  critical               |  Milestone:  PostGIS 2.2.2
 Component:  build/upgrade/install  |    Version:  2.2.x
Resolution:                         |   Keywords:
------------------------------------+---------------------------

Comment (by strk):

 My suspect is with different implementations of the _same_ signature being
 loaded in memory at the same time (due to both old and new postgis module
 loaded within the same process) and runtime linker picking one for the
 other, triggering Really Bad Things like this.

 The last time we fixed this by specifying --exlcude-libs (#3281) but I'm
 not sure it applies here, especially as old packages might still be
 exposing the methods outside.

 I guess one fix could be disabling the major-upgrade check (responsible of
 loading the old library), at least during EXTENSION upgrade (which should
 not allow upgrading between major releases, anyway).

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