Re: oid problem with dumping database (failed sanity check, opr with oid 280515 was not found)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Esger Abbink" <pggeneral(at)bumblebeast(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: oid problem with dumping database (failed sanity check, opr with oid 280515 was not found)
Date: 2002-01-16 15:57:42
Message-ID: 9455.1011196662@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Esger Abbink" <pggeneral(at)bumblebeast(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Doug McNaught 2002-01-16 16:06:16 Re: PQsendQuery: Query is too long
Previous Message Henrik Steffen 2002-01-16 15:38:54 PQsendQuery: Query is too long