Merlin Moncure-2 wrote:
>
> One proposed solution is to cache plpgsql plans around the search path.
>
I like the proposed solution, since search_path plays a part when generating
plpgsql plan, it make sense to be part of the cache.
Merlin Moncure-2 wrote:
>
> *) use sql functions for portions that float across schemas
>
Just to clarify, does this mean the sql functions doesn't cache plans like
plpgsql functions do?
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/plpgsql-function-confusing-behaviour-tp4576354p4579619.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.