Re: Must a C state transition function use palloc on the returned value? - Mailing list pgsql-hackers

From Dirk Lutzebaeck
Subject Re: Must a C state transition function use palloc on the returned value?
Date
Msg-id 14860.4233.534788.378482@ampato.core.aeccom.com
Whole thread Raw
In response to Re: Must a C state transition function use palloc on the returned value?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane writes:> Dirk Lutzebaeck <lutzeb@aeccom.com> writes:> > I'm defining a new aggregate using a C transition
function.It is of> > type TEXT, so the C function gets pointers (*text) to the internal-state1 and> > next-data-item
parameters.> > > Question is if the returning value of type *text must be palloc'ed or> > can be just taken from the
inputparameters.> > The result must be a fresh palloc, since both inputs will be pfreed the> moment you return.  7.1
willcopy the result for you if you are so> incautious as to try to return an input, but 7.0.* just falls over :-(
 

Thanks! It works now...

Dirk



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Must a C state transition function use palloc on the returned value?
Next
From: Peter Eisentraut
Date:
Subject: Re: Unhappy thoughts about pg_dump and objects inherited from template1