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 22059.1046637826@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() ?  (Kevin Brown <kevin@sysexperts.com>)
List pgsql-hackers
Itai Zukerman <zukerman@math-hat.com> writes:
> After recompiling with --enable-cassert, nserting into an empty table,
> I get:

>   TRAP: FailedAssertion("!((VfdCache[0].fd == (-1)))", File: "fd.c", Line: 1113)

Begins to look like a plain old wild store: ain't *nothing* should ever
write into VfdCache[0].fd.  If that's repeatable, you could try homing
in on the place that is clobbering that variable by stepping through
major routines with gdb.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Itai Zukerman
Date:
Subject: Re: GiST: Bad newtup On Exit From gistSplit() ?
Next
From: Kevin Brown
Date:
Subject: Re: GiST: Bad newtup On Exit From gistSplit() ?