From: | "Gurjeet Singh" <singh(dot)gurjeet(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "PGSQL Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Facing a problem with SPI |
Date: | 2006-12-04 15:32:50 |
Message-ID: | 65937bea0612040732x61e260dq9a88a5d275db5003@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 12/4/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> > we should remember the CurrentResourceOwner
> > across BIST() and RARCST() calls!
>
> As indeed the current callers of them do...
>
Thanks. I missed that piece of code in pl/pgsql exception handling!!!
So, if I use kludge the code like:
oldResourceOwner = CurrentResourceOwner;
BIST();
... do stuff ...
RARCST();
CurrentResourceOwner = oldResourceOwner;
it would be a standard way of doing it.
Best regards,
--
gurjeet[(dot)singh](at)EnterpriseDB(dot)com
singh(dot)gurjeet(at){ gmail | hotmail | yahoo }.com
From | Date | Subject | |
---|---|---|---|
Next Message | Florian G. Pflug | 2006-12-04 16:40:42 | Re: Notify enhancement |
Previous Message | Tom Lane | 2006-12-04 15:23:19 | Re: Facing a problem with SPI |