Re: Is there a way around function search_path killing SQL function inlining? - and backup / restore issue - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: Is there a way around function search_path killing SQL function inlining? - and backup / restore issue
Date
Msg-id 56E36445.3050303@BlueTreble.com
Whole thread Raw
In response to Re: Is there a way around function search_path killing SQL function inlining? - and backup / restore issue  ("Regina Obe" <lr@pcorp.us>)
Responses Re: Is there a way around function search_path killing SQL function inlining? - and backup / restore issue
List pgsql-hackers
On 3/10/16 3:29 PM, Regina Obe wrote:
> Take for example, I have tiger geocoder which relies on fuzzystrmatch.  I have no idea where someone installs
fuzzystrmatchso I can't schema qualify those calls.  I use that dependent function to use to build an index on tables.
 

This is something I've thought about as well, and I think the real 
problem is search_path just isn't the right way to handle this. I think 
there needs to be some way to definitively reference something that's 
part of an extension; a method that doesn't depend on whatever schema 
the extension happens to be installed in.
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com



pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: amcheck (B-Tree integrity checking tool)
Next
From: Peter Geoghegan
Date:
Subject: Re: amcheck (B-Tree integrity checking tool)