Re: TRAP: FailedAssertion("!((itemid)->lp_flags & 0x01)", File: "nbtsearch.c", Line: 89) - Mailing list pgsql-hackers

From Jim C. Nasby
Subject Re: TRAP: FailedAssertion("!((itemid)->lp_flags & 0x01)", File: "nbtsearch.c", Line: 89)
Date
Msg-id 20051026213947.GI16682@pervasive.com
Whole thread Raw
In response to Re: TRAP: FailedAssertion("!((itemid)->lp_flags & 0x01)", File: "nbtsearch.c", Line: 89)  (Martijn van Oosterhout <kleptog@svana.org>)
Responses Re: TRAP: FailedAssertion("!((itemid)->lp_flags & 0x01)", File: "nbtsearch.c", Line: 89)
List pgsql-hackers
On Wed, Oct 26, 2005 at 11:14:17PM +0200, Martijn van Oosterhout wrote:
> On Wed, Oct 26, 2005 at 04:03:41PM -0500, Jim C. Nasby wrote:
> > Is this something that should be logged better than it is? Is there any
> > value in trying to save the index/table that's busted?
> 
> Unfortuatly, it's one of those Assert(expr) lines, they don't generally
> give the opportunity for extra debug data. They're usually not even
> compiled in...
> 
> > Yeah, looks like no core files yet (they would be in $PGDATA somewhere,
> > correct?), so I had them hack their startup script to include ulimit -c
> > unlimited. Luckily this is pretty reproducable, so hopefully we'll have
> > a core soon.
> 
> Well, you know the query that generates it? EXPLAIN should tell you the
> indexes it's using, so you could just REINDEX those...

Well, since query logging only logs when a query finishes...

> Or REINDEX them all... :)

242G database. That would take quite a while... :)
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461


pgsql-hackers by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: sort_mem statistics ...
Next
From: Tom Lane
Date:
Subject: Re: TRAP: FailedAssertion("!((itemid)->lp_flags & 0x01)", File: "nbtsearch.c", Line: 89)