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 | 20051026223625.GM16682@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)
|
Список | 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. > > > 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). Reproduced the crash, but still no core file... where exactly should it have been put? Would in be outside of $PGDATA? Is there any way to verify the ulimit setings that the backend is running under? -- 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 по дате отправления: