Re: problem with varlena and extended type

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: problem with varlena and extended type
Date: 2009-07-04 21:46:07
Message-ID: 407d949e0907041446p6e24afb3m8e6c5c5ff9c9960f@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Jul 4, 2009 at 10:31 PM, Greg Stark<gsstark(at)mit(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2009-07-04 22:13:50 Re: commitfest.postgresql.org
Previous Message Greg Stark 2009-07-04 21:31:21 Re: problem with varlena and extended type