pg.ddx.io pgsql-admin@postgresql.org mailing list archivehelp / color / mirror / Atom feed
ERROR: cache lookup failed for type 16292881 2+ messages / 2 participants [nested] [flat]
* ERROR: cache lookup failed for type 16292881 @ 2019-12-03 12:55 Ramiro Barreca <rbarreca@gmail.com> 2019-12-03 15:23 ` Re: ERROR: cache lookup failed for type 16292881 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 1 reply; 2+ messages in thread From: Ramiro Barreca @ 2019-12-03 12:55 UTC (permalink / raw) To: pgsql-admin@lists.postgresql.org 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 There are several databases in this server, but this is the only one that produces this FAIL. Reported message from pg_dump is: *(...)* *pg_dump: reading triggers for table "usuario_sistema_externo"* *pg_dump: reading dependency data* *pg_dump: saving encoding = UTF8* *pg_dump: saving standard_conforming_strings = on* *pg_dump: saving database definition* *pg_dump: SQL command failed* *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* *pg_dump: *** aborted because of error* We 've found no one type with this OID. Looking at a solution in several forums, speaks about objects dropped in replication platforms, but it is not this case. Any help to know where to look for? Thank you.. Ramiro Barreca rbarreca@gmail.com ^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: ERROR: cache lookup failed for type 16292881 2019-12-03 12:55 ERROR: cache lookup failed for type 16292881 Ramiro Barreca <rbarreca@gmail.com> @ 2019-12-03 15:23 ` Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 2+ messages in thread From: Tom Lane @ 2019-12-03 15:23 UTC (permalink / raw) To: Ramiro Barreca <rbarreca@gmail.com>; +Cc: pgsql-admin@lists.postgresql.org 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 ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2019-12-03 15:23 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2019-12-03 12:55 ERROR: cache lookup failed for type 16292881 Ramiro Barreca <rbarreca@gmail.com> 2019-12-03 15:23 ` Re: ERROR: cache lookup failed for type 16292881 Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox