Re: plpgsql function confusing behaviour - Mailing list pgsql-general

From Merlin Moncure
Subject Re: plpgsql function confusing behaviour
Date
Msg-id CAHyXU0z6yGeyKiOeTbm=e1EgWk4fgu5xbTUcCfJQ9WnU6bNSsw@mail.gmail.com
Whole thread Raw
In response to Re: plpgsql function confusing behaviour  (Shianmiin <Shianmiin@gmail.com>)
List pgsql-general
On Tue, Jul 12, 2011 at 12:10 PM, Shianmiin <Shianmiin@gmail.com> 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:
>>
>> *) 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?

correct. so you could wrap schema dependent bits inside set returning
sql functions.

merlin

pgsql-general by date:

Previous
From: Willy-Bas Loos
Date:
Subject: Re: dirty read from plpgsql
Next
From: Lars Kanis
Date:
Subject: Using LDAP roles in PostgreSQL