[postgis-tickets] [PostGIS] #4271: postgis_extensions_upgrade() does nothing when upgrading from same version of Postgis different PostgreSQL

[PostGIS]

#4271: postgis_extensions_upgrade() does nothing when upgrading from same version
of Postgis different PostgreSQL
------------------------------------+---------------------------
  Reporter:  robe                   |      Owner:  robe
      Type:  defect                 |     Status:  new
  Priority:  medium                 |  Milestone:  PostGIS 2.5.2
 Component:  build/upgrade/install  |    Version:  2.5.x
Resolution:                         |   Keywords:
------------------------------------+---------------------------

Comment (by robe):

 I don't think we need a force, we just want to do the next dance whenever
 we see the PostgreSQL versions are different.

 We have the next for production versions too and it works.  In the case of
 people pg_upgrading from same PostGIS version older PostgreSQL to same
 PostGIS version to newer PostgreSQL, this is going to be a pretty common
 occurrence.  Let's not confuse them further by telling them they need to
 do "force".

 IT's too late to introduce a force in PostGIS 2.5 since we can't make API
 changes.  We COULD have a force in PostGIS 3.0.  Though I'm thinking under
 what circumstances would I need a force (aside from the dev case and the
 "When I'm upping my PostgreSQL game, but not my PostGIS game"

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