Re: cleaning up in UDF's (user-defined functions)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: craig perras <craigp98072(at)yahoo(dot)com>
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: cleaning up in UDF's (user-defined functions)
Date: 2004-06-09 14:53:41
Message-ID: 21081.1086792821@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-interfaces

craig perras <craigp98072(at)yahoo(dot)com> writes:
> 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?

What resources? Most stuff (like palloc'd memory) is taken care of
for you. If you're maintaining your own private permanent data
structures then you may need to plug in a transaction-end hook
routine to clean those up.

pgsql-interfaces is hardly the place for discussing how to write
C-language server functions; if you want to discuss the fine points
I'd suggest pgsql-hackers.

regards, tom lane

In response to

Browse pgsql-interfaces by date

  From Date Subject
Next Message David Stanaway 2004-06-09 21:44:12 Problem with PQexecPrepared
Previous Message craig perras 2004-06-09 02:29:08 cleaning up in UDF's (user-defined functions)