From: Tom Lane <tgl@sss.pgh.pa.us>
To: Cory Nemelka <cnemelka@gmail.com>
cc: pgsql-admin@postgresql.org
Subject: Re: Error accessing catalog table pg_proc
In-reply-to: 
 <CAMe5Gn12H8FWyo3-+H1kbZZu3gafPg2uE2sTn9Xq-ytteToy1w@mail.gmail.com>
References: 
 <CAMe5Gn12H8FWyo3-+H1kbZZu3gafPg2uE2sTn9Xq-ytteToy1w@mail.gmail.com>
Comments: In-reply-to Cory Nemelka <cnemelka@gmail.com>
	message dated "Wed, 08 Nov 2017 11:07:49 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <390.1510172858.1@sss.pgh.pa.us>
Date: Wed, 08 Nov 2017 15:27:38 -0500
Message-ID: <391.1510172858@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Cory Nemelka <cnemelka@gmail.com> writes:
> We are receiving the following error when trying to access pg_proc table:
> [local] cnemelka=# \d pg_proc;
> ERROR:  XX000: cache lookup failed for attribute 1 of relation 1255
> LOCATION:  get_relid_attribute_name, lsyscache.c:807

> This error is preventing backups with pg_dump.  It doesn't seem to be
> affecting the database overall.  We ran VACUUM FULL and REINDEX on the
> catalog tables but the error persists.

Hmm, did you reindex pg_attribute in particular?  Because that's where the
apparently missing data is.

I'm afraid VACUUM FULL would've destroyed any evidence of what went wrong,
but conceivably you could reinsert the missing row(s) by copying from
another database in the cluster.  pg_attribute rows for system catalogs
should be the same across all databases.

			regards, tom lane


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin