From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Dirk Lutzebaeck <lutzeb(at)aeccom(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: cannot find attribute 1 of relation (of some user table) in 7.1.3 |
Date: | 2002-01-13 23:45:20 |
Message-ID: | 29250.1010965520@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Dirk Lutzebaeck <lutzeb(at)aeccom(dot)com> writes:
> Hi, I have the follow problem when vacuum'ing on 7.1.3:
> ERROR: cannot find attribute 1 of relation docmatchsel
> Then I tried to reindex the table in standalone mode which gives:
> backend> reindex table docmatchsel force
> ERROR: catalog is missing 4 attributes for relid 117042636
Bizarre. Were there four columns altogether?
> docmatchsel was created as a temporary table in the application.
Since it's only a temporary table, my counsel is:
1. delete from pg_class where relname = 'docmatchsel';
2. pg_dump, initdb, reload.
You might be okay after just step 1, but given that we don't know what
caused this, an initdb seems like a good idea.
It would be interesting to go groveling through pg_attribute and see if
we can find any traces of the missing attribute rows, but unless you're
prepared to sift through the bits yourself (or give access to some
developer to do it), that's not going to happen.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Sandor Vig | 2002-01-14 07:23:12 | Va: Bug #560: ODBC problem at migrating 7.0 to 7.1 |
Previous Message | Dirk Lutzebaeck | 2002-01-13 20:52:38 | cannot find attribute 1 of relation (of some user table) in 7.1.3 |