On Tue, Jul 12, 2011 at 12:10 PM, Shianmiin wrote:
>
> 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:
>
> 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 porti
On Mon, Jul 11, 2011 at 3:23 PM, Shianmiin wrote:
> We have recently gone thru an unexpected behavior of PostgreSQL function
> written in plpgsql.
> I wonder if anyone can help explain the ideas behind the design.
>
> Test scenario:
> 1. create two identical schemas, let's call them tenant1 and te
