>>>>> "Dimitri" == Dimitri Fontaine <dfonta...@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 having Dimitri> user schemas with the implicit capability too? Dimitri> Then you have the problem of ordering more than one implicit Dimitri> 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. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
