Re: Must a C state transition function use palloc on the returned value?

From: Dirk Lutzebaeck <lutzeb(at)aeccom(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Must a C state transition function use palloc on the returned value?
Date: 2000-11-10 15:13:13
Message-ID: 14860.4233.534788.378482@ampato.core.aeccom.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane writes:
> Dirk Lutzebaeck <lutzeb(at)aeccom(dot)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 input parameters.
>
> The result must be a fresh palloc, since both inputs will be pfreed the
> moment you return. 7.1 will copy 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2000-11-10 16:24:54 Re: Unhappy thoughts about pg_dump and objects inherited from template1
Previous Message Tom Lane 2000-11-10 15:03:07 Re: Must a C state transition function use palloc on the returned value?