Re: oid problem with dumping database (failed sanity check, opr with oid 280515 was not found) - Mailing list pgsql-general

From Tom Lane
Subject Re: oid problem with dumping database (failed sanity check, opr with oid 280515 was not found)
Date
Msg-id 9455.1011196662@sss.pgh.pa.us
Whole thread Raw
In response to oid problem with dumping database (failed sanity check, opr with oid 280515 was not found)  ("Esger Abbink" <pggeneral@bumblebeast.com>)
List pgsql-general
"Esger Abbink" <pggeneral@bumblebeast.com> writes:
> i have a problem dumping a db. somewhere along the way pg_dump stops with the following error:

> failed sanity check, opr with oid 280515 was not found

You have an operator whose oprcom, oprnegate, oprlsortop, or oprrsortop
field points at a no-longer-existing operator.  Look in pg_operator for
the row(s) mentioning that OID and get rid of those operators too.
(Or, manually set the fields to 0 if you want to keep the operators that
have the dangling pointers.)

            regards, tom lane

pgsql-general by date:

Previous
From: Henrik Steffen
Date:
Subject: PQsendQuery: Query is too long
Next
From: Doug McNaught
Date:
Subject: Re: PQsendQuery: Query is too long