Re: GiST: Bad newtup On Exit From gistSplit() ? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: GiST: Bad newtup On Exit From gistSplit() ?
Date
Msg-id 18875.1046629271@sss.pgh.pa.us
Whole thread Raw
In response to Re: GiST: Bad newtup On Exit From gistSplit() ?  (Itai Zukerman <zukerman@math-hat.com>)
Responses Re: GiST: Bad newtup On Exit From gistSplit() ?  (Itai Zukerman <zukerman@math-hat.com>)
List pgsql-hackers
Itai Zukerman <zukerman@math-hat.com> writes:
> I'm still not having any luck tracking down my SEGV.  If anyone is
> interested in debugging or even just reproducing this, I'd be happy to
> post or E-mail you my code.  It looks like shortly after calling
> gistSplit() there's maybe a double-free() somewhere?

It might help to build with --enable-cassert, if you didn't already.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: System Tables and Triggers
Next
From: Tom Lane
Date:
Subject: CLUSTER loses nulls (was Re: [ADMIN] Still a bug in the VACUUM)