[postgis-tickets] [PostGIS] #3076: Unqualified function calls break postgres_fdw compatibiliy

[PostGIS]

#3076: Unqualified function calls break postgres_fdw compatibiliy
----------------------+-----------------------------------------------------
 Reporter:  fphilipe  |       Owner:  pramsey
     Type:  defect    |      Status:  new    
 Priority:  medium    |   Milestone:         
Component:  postgis   |     Version:  2.1.x  
 Keywords:            |  
----------------------+-----------------------------------------------------

Comment(by robe):

 This is the same case as #2485, and some others we have in the system
 (which I can't find at the moment) so not specific to postgres_fdw.  The
 issue is with PostGIS functions that call other PostGIS functions or
 tables.

 I was thinking about this a lot lately and thinking the only none-breaking
 change we could make was to as part of the function, add the common
 schemas people install these in to the search path of the functions in
 question.

 It's only functions that reference other functions (or tables) that are
 affected by this issue.  Things like ST_Distance, a bunch of the raster
 contraint functions, ST_Transform, ST_Buffer, ST_DWithin.

 I have to bring it up for vote and also do some more tests with this idea,
 but as far as I can tell, PostgreSQL is okay with specifying non-existent
 schemas in the search path.

 So if we go with the standard schemas people install PostGIS in -- public,
 postgis, contrib we should be okay.  I haven't run across any other
 schemas people use to install postgis in, but doing such a thing would be
 a breaking change for these folks.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/3076#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.