From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ramiro Barreca <rbarreca@gmail.com>
cc: pgsql-admin@lists.postgresql.org
Subject: Re: ERROR: cache lookup failed for type 16292881
In-reply-to: 
 <CAO4Rs2ktcz3UecyHXP1CsJzqL4k0DfUZa_rvUg5v2D6XuJA_Mg@mail.gmail.com>
References: 
 <CAO4Rs2ktcz3UecyHXP1CsJzqL4k0DfUZa_rvUg5v2D6XuJA_Mg@mail.gmail.com>
Comments: In-reply-to Ramiro Barreca <rbarreca@gmail.com>
	message dated "Tue, 03 Dec 2019 09:55:15 -0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <32504.1575386636.1@sss.pgh.pa.us>
Date: Tue, 03 Dec 2019 10:23:56 -0500
Message-ID: <32505.1575386636@sss.pgh.pa.us>
Precedence: bulk

Ramiro Barreca <rbarreca@gmail.com> writes:
> Since a few days ago we are having problems while performing backup using
> pg_dump to a PG 8.4 database over a Centos 5.5

You realize of course that 8.4.anything is long out of support, and
therefore full of known bugs.  But I wonder whether this is even a
reasonably late minor release of 8.4.

> *pg_dump: Error message from server: ERROR:  cache lookup failed for type
> 16292881*
> *pg_dump: The command was: SELECT proretset, prosrc, probin,
> pg_catalog.pg_get_function_arguments(oid) AS funcargs,
> pg_catalog.pg_get_function_identity_arguments(oid) AS funciargs,
> pg_catalog.pg_get_function_result(oid) AS funcresult, proiswindow,
> provolatile, proisstrict, prosecdef, proconfig, procost, prorows, (SELECT
> lanname FROM pg_catalog.pg_language WHERE oid = prolang) AS lanname FROM
> pg_catalog.pg_proc WHERE oid = '16292882'::pg_catalog.oid*

You might learn something productive from

select * from pg_proc where oid = '16292882';

The direct problem of course is that oid 16292881 can't be found
in pg_type.  If you're really lucky, that's just index corruption
that could be fixed by reindexing pg_type.

			regards, tom lane