Re: ERROR: cache lookup failed for type 16292881 - Mailing list pgsql-admin

From Tom Lane
Subject Re: ERROR: cache lookup failed for type 16292881
Date
Msg-id 32505.1575386636@sss.pgh.pa.us
Whole thread Raw
In response to ERROR: cache lookup failed for type 16292881  (Ramiro Barreca <rbarreca@gmail.com>)
List pgsql-admin
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



pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: Should I care about this error "failed to link /usr/bin/psql [...] exists and it is not a symlink"?
Next
From: Ekaterina Amez
Date:
Subject: Re: Should I care about this error "failed to link /usr/bin/psql[...] exists and it is not a symlink"?