Re: contrib function naming, and upgrade issues - Mailing list pgsql-hackers

From Andrew Gierth
Subject Re: contrib function naming, and upgrade issues
Date
Msg-id 87tz5lvt3j.fsf@news-spur.riddles.org.uk
Whole thread Raw
In response to Re: contrib function naming, and upgrade issues  (Dimitri Fontaine <dfontaine@hi-media.com>)
List pgsql-hackers
>>>>> "Dimitri" == Dimitri Fontaine <dfontaine@hi-media.com> writes:
>> Partly that's based on the relative inflexibility of the>> search_path setting; it's hard to modify the search_path
without>>completely replacing it, so knowledge of the "default" search path>> ends up being propagated to a lot of
places.
Dimitri> pg_catalog is implicit in the search_path, what about havingDimitri> user schemas with the implicit capability
too?
Dimitri> Then you have the problem of ordering more than one implicitDimitri> schemas,

This is a hint that it's really a bad idea.

Instead, what I'd suggest is breaking up search_path into multiple
variables - maybe pre_search_path, search_path, and
post_search_path.

-- 
Andrew.


pgsql-hackers by date:

Previous
From: Andrew Gierth
Date:
Subject: Re: contrib function naming, and upgrade issues
Next
From: Andrew Gierth
Date:
Subject: Re: contrib function naming, and upgrade issues