Tatsuo Ishii <[EMAIL PROTECTED]> writes:
>> Because with the current definition, any change in search_path really
>> ought to lead to repeating the lookup for the default conversion proc.
>> That's a bad idea from a performance point of view and I don't think
>> it's a particularly good idea from the definitional point of view
>> either --- do you really want the client conversion changing because
>> some function altered the search path?
> That argument does not strike me too strongly. I cannot imagine the
> case search_path changed so frequently.
I can. There's been talk for example of having a search path associated
with every function definition, so that it might need to be changed at
every function call and return. In any case I don't like the notion
that the client conversion is tied to search_path; they really should
be independent.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
