Re: problem with varlena and extended type - Mailing list pgsql-hackers

From Greg Stark
Subject Re: problem with varlena and extended type
Date
Msg-id 407d949e0907041446p6e24afb3m8e6c5c5ff9c9960f@mail.gmail.com
Whole thread Raw
In response to Re: problem with varlena and extended type  (Greg Stark <gsstark@mit.edu>)
Responses Re: problem with varlena and extended type  (Pavel Stehule <pavel.stehule@gmail.com>)
Re: problem with varlena and extended type  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
On Sat, Jul 4, 2009 at 10:31 PM, Greg Stark<gsstark@mit.edu> wrote:
> It's pretty hard to guess where your bug is sitting here with no code
> and no idea even what you've done to trigger it.
>
> At a guess there someplace you haven't detoasted a datum that had to
> be detoasted. But like I said that's just a guess.
>

Actually on further thought I think this smells like a memory
management bug. Maybe you've either you've prematurely freed this data
structure or realloc'd it without tracking the new pointer and have
returned a pointer to the freed object.


-- 
greg
http://mit.edu/~gsstark/resume.pdf


pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: problem with varlena and extended type
Next
From: Peter Eisentraut
Date:
Subject: Re: commitfest.postgresql.org