Re: BUG #5769: Problem with SPI_getvalue - Mailing list pgsql-bugs

From Heikki Linnakangas
Subject Re: BUG #5769: Problem with SPI_getvalue
Date
Msg-id 4CEE7C87.50909@enterprisedb.com
Whole thread Raw
In response to BUG #5769: Problem with SPI_getvalue  ("Helmar Spangenberg" <hspangenberg@frey.de>)
Responses Re: BUG #5769: Problem with SPI_getvalue  (Helmar Spangenberg <hspangenberg@frey.de>)
List pgsql-bugs
On 25.11.2010 13:45, Helmar Spangenberg wrote:
> Bug reference:      5769
> Logged by:          Helmar Spangenberg
> Email address:      hspangenberg@frey.de
> PostgreSQL version: 9.0.1
> Operating system:   Linux
> Description:        Problem with SPI_getvalue
> Details:
>
> Referring to the manual, I can pfree the result returned by SPI_getvalue.
> However the backend crashes as soon as I use pfree.
>
> No example uses pfree. Could it be possible, there is a bug in the
> documentation?

The return value of SPI_getvalue is certainly palloc()'d, so pfree()ing
it should not crash. Perhaps you are trying to pfree() it after the
whole memory context has already been destroyed. Or perhaps SPI_getvalue
returned a NULL and you're trying to pfree() that. Can't say without
more details.

--
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com

pgsql-bugs by date:

Previous
From: "Helmar Spangenberg"
Date:
Subject: BUG #5769: Problem with SPI_getvalue
Next
From: Helmar Spangenberg
Date:
Subject: Re: BUG #5769: Problem with SPI_getvalue