Re: BUG #7881: SQL function failures in long-lived calling contexts

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: andrew(at)tao11(dot)riddles(dot)org(dot)uk
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #7881: SQL function failures in long-lived calling contexts
Date: 2013-03-03 22:18:02
Message-ID: 13304.1362349082@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

I wrote:
> Or we could add fields recording the current transaction/subtransaction
> IDs, then throw away and regenerate the function cache entry if that
> subxact is no longer active. This would be a bit more invasive/riskier
> than throwing a "not supported" error, but it would preserve the
> functionality.

The attached patch seems fairly reasonable for this.

regards, tom lane

Attachment Content-Type Size
sql-function-cache-fix.patch text/x-patch 8.8 KB

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Louis-Arnaud Iscla 2013-03-03 23:45:04 "Password" issues -- bug??
Previous Message Tom Lane 2013-03-03 19:27:44 Re: BUG #7881: SQL function failures in long-lived calling contexts