[postgis-tickets] [PostGIS] #3496: Make postgis non-relocateable and schema qualify at least core functions

[PostGIS]

#3496: Make postgis non-relocateable and schema qualify at least core functions
------------------------------------+---------------------------
  Reporter:  robe                   |      Owner:  robe
      Type:  defect                 |     Status:  new
  Priority:  high                   |  Milestone:  PostGIS 2.3.0
 Component:  build/upgrade/install  |    Version:  trunk
Resolution:                         |   Keywords:
------------------------------------+---------------------------

Comment (by strk):

 Sorry, figured (it's all explained in the summary).
 So basically via extension-install you decide the installation schema at
 "CREATE EXTENSION" time, and the same basically happens on non-extension-
 install (things are installed in the first schema of the search_path).

 The difference between extension and non-extension installs is that
 extension-install has internal calls all fully-qualified to the schema
 decided at installation time, while non-extension install do not.

 In turn, the above means that upgrade may still be broken for non-
 extension installs, right ?

 I'm a bit afraid of this difference between extension and non-extension
 install.
 Moving to hard-coded destination schema (decided at build time) should
 remove the difference, and we'd have all internal linking schema-
 qualified.

 Or, we should provide a postgis enabler-script to replace the manual load
 of the .sql files and provide the ability to specify target schema at that
 time. Would that be a too big of a change for non-extension installs ?

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