Re: Problem with database: FATAL 1: cannot find attribute 24
От | Tauren Mills |
---|---|
Тема | Re: Problem with database: FATAL 1: cannot find attribute 24 |
Дата | |
Msg-id | NBBBLBKDJMGDNPMDGAABMEEHBPAB.tauren@servlets.net обсуждение исходный текст |
Ответ на | Re: Problem with database: FATAL 1: cannot find attribute 24 (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-general |
Hi Tom, Thanks for the help! I'm afraid I do not know how to do this. Is there somewhere that specifically explains how to run a standalone backend under gdb? How would I set a breakpoint at elog or get a stack trace? Does the RPM version of Postgres include debugging symbols, or would I need to compile a separate version? Thanks! Tauren > -----Original Message----- > From: Tom Lane [mailto:tgl@sss.pgh.pa.us] > Sent: Monday, September 17, 2001 1:35 PM > To: Tauren Mills > Cc: Martijn van Oosterhout; Justin Clift; PostgreSQL General Mailing > List > Subject: Re: [GENERAL] Problem with database: FATAL 1: cannot find > attribute 24 > > > "Tauren Mills" <tauren@servlets.net> writes: > > Then, I try running postgres like this: > > bash$ postgres -d 5 -D /var/lib/pgsql/data dans_pgsql > > AATAL 1: cannot find attribute 24 of relation > > Since there aren't any system catalogs with as many as 24 columns, the > problem is clearly a level or two down from where the error is being > reported. Try running that standalone backend under gdb with a > breakpoint set at elog, and get a stack trace when the error is reached. > (Note that each of the "debug" messages also goes through elog, so the > first elog entry is not the one you want.) > > You might have to recompile with debugging symbols enabled to get any > useful information from gdb. > > regards, tom lane >
В списке pgsql-general по дате отправления: