Re: problem with varlena and extended type

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