From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | FOUTE K(dot) Jaurès <jauresfoute(at)gmail(dot)com> |
Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: PostgreSQL 12 - ERROR: invalid attribute number 2 for ad_user_pkey - Urgent |
Date: | 2021-09-01 15:46:41 |
Message-ID: | 2077430.1630511201@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
=?UTF-8?Q?FOUTE_K=2E_Jaur=C3=A8s?= <jauresfoute(at)gmail(dot)com> writes:
> For all table except the pg_catalo table.
> The dump on the database is not possible too. (pg_dump: error: invalid
> column numbering in table "xxxxxx")
It seems that pg_attribute is messed up. If you are really lucky,
it might be only a problem in pg_attribute's indexes, in which case
reindexing pg_attribute would fix it. However, I recommend proceeding
on the assumption that you have possibly-irrecoverable damage. Before
you do ANYTHING, make a complete filesystem-level backup of the cluster
(stop the server, then do "tar cf backup.tar $PGDATA" or equivalent).
Even if reindexing pg_attribute seems to fix it, I'd counsel then doing
a pg_dump and restore, in hopes of curing any other problems that may
have stemmed from the same root cause.
Speaking of root cause, have you had any crashes lately? Is your
Postgres up-to-date? How about the underlying OS?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Mario Emmenlauer | 2021-09-01 15:49:57 | Re: dup(0) fails on Ubuntu 20.04 and macOS 10.15 with 13.0 |
Previous Message | David G. Johnston | 2021-09-01 15:40:03 | Re: PostgreSQL 12 - ERROR: invalid attribute number 2 for ad_user_pkey - Urgent |