After running: REINDEX TABLE pg_catalog.pg_attribute ;
Le mer. 1 sept. 2021 à 17:54, FOUTE K. Jaurès <jauresfoute@xxxxxxxxx> a écrit :
Hello Tom,Thank You for your Answer. It solves the problem.Thank you very much for your support.Le mer. 1 sept. 2021 à 16:46, Tom Lane <tgl@xxxxxxxxxxxxx> a écrit :=?UTF-8?Q?FOUTE_K=2E_Jaur=C3=A8s?= <jauresfoute@xxxxxxxxx> 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
--Jaurès FOUTE
Jaurès FOUTE
