| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Tauren Mills" <tauren(at)servlets(dot)net> |
| Cc: | "Martijn van Oosterhout" <kleptog(at)svana(dot)org>, "Justin Clift" <justin(at)postgresql(dot)org>, "PostgreSQL General Mailing List" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Problem with database: FATAL 1: cannot find attribute 24 |
| Date: | 2001-09-17 20:34:48 |
| Message-ID: | 11045.1000758888@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Tauren Mills" <tauren(at)servlets(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martín Marqués | 2001-09-17 20:49:50 | Re: locale and spanish acute |
| Previous Message | mike | 2001-09-17 20:26:12 | Re: a plpgsql programming question |