cleaning up in UDF's (user-defined functions) - Mailing list pgsql-interfaces

From craig perras
Subject cleaning up in UDF's (user-defined functions)
Date
Msg-id 20040609022908.43286.qmail@web21208.mail.yahoo.com
Whole thread Raw
Responses Re: cleaning up in UDF's (user-defined functions)
List pgsql-interfaces
I appended an excerpt from the docs... IIUC, if I make
a DSQL call from a UDF (written in C), and there's a
transaction abort caused by that command, then my
function is never called back. How do I cleanup any
resources the function allocated if this is the case?

I'm not even sure how I could NOTIFY clients, since
the transaction aborted.

thanks!
--craig

Note that if during the execution of a procedure the
transaction is aborted because of an error in a
command, then control will not be returned to your
procedure. Rather, all work will be rolled back and
the server will wait for the next command from the
client. A related restriction is the inability to
execute BEGIN, COMMIT, and ROLLBACK (transaction
control statements) inside a procedure. Both of these
restrictions will probably be changed in the future.


    
__________________________________
Do you Yahoo!?
Friends.  Fun.  Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/ 


pgsql-interfaces by date:

Previous
From: L J Bayuk
Date:
Subject: Re: Is there a way to describe precision and scale
Next
From: Tom Lane
Date:
Subject: Re: cleaning up in UDF's (user-defined functions)