Postgres Pro
Downloads
Home   >   mailing lists

Re: Facing a problem with SPI - Mailing list pgsql-hackers

From Gurjeet Singh
Subject Re: Facing a problem with SPI
Date
Msg-id 65937bea0612040732x61e260dq9a88a5d275db5003@mail.gmail.com
Whole thread Raw
In response to Re: Facing a problem with SPI  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view
On 12/4/06, Tom Lane <tgl@sss.pgh.pa.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[.singh]@EnterpriseDB.com
singh.gurjeet@{ gmail | hotmail | yahoo }.com

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Facing a problem with SPI
Next
From: "Timasmith"
Date:
Subject: Re: postgresql roadmap for horizontal scalability?