Re: problem with varlena and extended type

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

2009/7/4 Greg Stark <gsstark(at)mit(dot)edu>:
> 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.

good shot - I had problem with repalloc

thank you very much
Pavel

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Gregory Maxwell 2009-07-05 08:15:22 Re: Multi-Dimensional Histograms
Previous Message Brendan Jurd 2009-07-05 06:54:56 Re: commitfest.postgresql.org