Skip site navigation (1) Skip section navigation (2)

Re: GiST: Bad newtup On Exit From gistSplit() ?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Itai Zukerman <zukerman(at)math-hat(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: GiST: Bad newtup On Exit From gistSplit() ?
Date: 2003-03-02 20:43:46
Message-ID: 22059.1046637826@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Itai Zukerman <zukerman(at)math-hat(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Kevin BrownDate: 2003-03-02 21:43:34
Subject: Re: GiST: Bad newtup On Exit From gistSplit() ?
Previous:From: Itai ZukermanDate: 2003-03-02 19:31:06
Subject: Re: GiST: Bad newtup On Exit From gistSplit() ?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group