Re: pgsql: Remove inappropriate memory context switch in

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-hackers(at)postgresql(dot)org
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Remove inappropriate memory context switch in
Date: 2008-11-30 21:29:03
Message-ID: 12421.1228080543@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

"Neil Conway" <neilc(at)samurai(dot)com> writes:
> On Sun, Nov 30, 2008 at 1:09 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Well, dblink is simply calling SRF_RETURN_DONE() when the current
> context is the multi-call memory context.

So I see.

> We could outlaw that
> practice, but that risks breaking out-of-tree SRFs that do something
> similar.

No, they're already broken; this is just making the breakage more
obvious. It is not kosher for a SQL-callable function to return with
a different current context than it was called in.

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2008-11-30 23:07:09 Re: pgsql: Remove inappropriate memory context switch in
Previous Message Neil Conway 2008-11-30 21:26:17 Re: pgsql: Remove inappropriate memory context switch in

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-11-30 23:07:09 Re: pgsql: Remove inappropriate memory context switch in
Previous Message Neil Conway 2008-11-30 21:26:17 Re: pgsql: Remove inappropriate memory context switch in