Re: TRAP: FailedAssertion("!((itemid)->lp_flags & 0x01)", File: "nbtsearch.c", Line: 89)
От | Jim C. Nasby |
---|---|
Тема | Re: TRAP: FailedAssertion("!((itemid)->lp_flags & 0x01)", File: "nbtsearch.c", Line: 89) |
Дата | |
Msg-id | 20051026210341.GF16682@pervasive.com обсуждение исходный текст |
Ответ на | Re: TRAP: FailedAssertion("!((itemid)->lp_flags & 0x01)", File: "nbtsearch.c", Line: 89) (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: TRAP: FailedAssertion("!((itemid)->lp_flags & 0x01)", File: "nbtsearch.c", Line: 89)
Re: TRAP: FailedAssertion("!((itemid)->lp_flags & 0x01)", File: "nbtsearch.c", Line: 89) |
Список | pgsql-hackers |
On Wed, Oct 26, 2005 at 04:48:22PM -0400, Tom Lane wrote: > "Jim C. Nasby" <jnasby@pervasive.com> writes: > > TRAP: FailedAssertion("!((itemid)->lp_flags & 0x01)", File: "nbtsearch.c", Line: 89) > > > Looking through the code I see that's something to do with indexes, but > > I'm not sure what. Is this likely a corrupted index? > > Sounds that way. 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? This is 8.0.3, btw. > > If so, is there some way I could identify which index? > > gdb the core file and do "p rel->rd_rel->relname" in the _bt_search > stack frame (which is not going to be the top of stack but should be > close to the top). 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. -- 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 по дате отправления: