[postgis-tickets] [PostGIS] #4170: ERROR: Upgrade of postgis from version 2.1.9 r15770 to version 3.0 requires a dump/reload. See PostGIS manual for instructions

[PostGIS]

#4170: ERROR: Upgrade of postgis from version 2.1.9 r15770 to version 3.0 requires
a dump/reload. See PostGIS manual for instructions
----------------------+---------------------------
  Reporter:  strk     |      Owner:  pramsey
      Type:  defect   |     Status:  new
  Priority:  medium   |  Milestone:  PostGIS 2.4.5
 Component:  postgis  |    Version:  2.4.x
Resolution:           |   Keywords:
----------------------+---------------------------

Comment (by strk):

 The message comes from a check produced by utils/postgis_proc_upgrade.pl,
 specifically added to avoid incompatible upgrades:
 {{{
   IF old_maj != new_maj THEN
     RAISE EXCEPTION ''Upgrade of MODULE from version % to version %
 requires a dump/reload. See PostGIS manual for instructions'',
 old_scripts, new_scripts;
   ELSE
     RETURN ''Scripts versions checked for upgrade: ok'';
   END IF;
 }}}

 Theoretically, that check should make loading postgis_ugrade.sql safe
 (doing nothing) when the target version is a major version higher than the
 source version of PostGIS, assuming a change in Major version will always
 only occur when the storage format changes, and thus assuming that
 changing input/output functions would in this case result in an unusable
 database.

 As we changed Major version w/out such an occurrence we should ask
 ourselves whether we want to change semantic of Major version OR we want
 to differently determine if dump/reload is required in order NOT to brick
 someone's database...

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