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

Started by Esger Abbinkabout 24 years ago10 messagesgeneral
Jump to latest
#1Esger Abbink
pggeneral@bumblebeast.com

Hi,

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

i have found some references to this or similar problems but cant find a fix anywhere.

the postgres version is 7.0.3 (i'd upgrade if i could ;) )

Esger

--
NeoMail - Webmail that doesn't suck... as much.
http://neomail.sourceforge.net

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Esger Abbink (#1)
Re: oid problem with dumping database (failed sanity check, opr with oid 280515 was not found)

"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

#3Esger Abbink
pggeneral@bumblebeast.com
In reply to: Tom Lane (#2)
Re: oid problem with dumping database (failed sanity check, opr with oid 280515 was not found)

"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

It indeed turned out to be a stale reference. Probably the operator was dropped and reloaded without recreating all other referring operators (i guess thats the way to prevent this problem).

Thanks for the hint :)

btw, is there a way to get an overview of all created functions (i assume pg_operator lists all operators and thus all results of CREATE OPERATOR .., where does CREATE FUNCTION .. end up?
(if i missed this in manuals somewhere please save yourself the typing and just point me ;) )

Esger

--
NeoMail - Webmail that doesn't suck... as much.
http://neomail.sourceforge.net

#4Esger Abbink
pggeneral@bumblebeast.com
In reply to: Esger Abbink (#3)
Re: oid problem with dumping database (failed sanity check, opr with oid 280515 was not found)

"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

It indeed turned out to be a stale reference. Probably the operator was dropped and reloaded without recreating all other referring operators (i guess thats the way to prevent this problem).

Thanks for the hint :)

btw, is there a way to get an overview of all created functions (i assume pg_operator lists all operators and thus all results of CREATE OPERATOR .., where does CREATE FUNCTION .. end up?
(if i missed this in manuals somewhere please save yourself the typing and just point me ;) )

Esger

--
NeoMail - Webmail that doesn't suck... as much.
http://neomail.sourceforge.net

#5Esger Abbink
pggeneral@bumblebeast.com
In reply to: Esger Abbink (#4)
Re: oid problem with dumping database (failed sanity check, opr with oid 280515 was not found)

"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

It indeed turned out to be a stale reference. Probably the operator was dropped and reloaded without recreating all other referring operators (i guess thats the way to prevent this problem).

Thanks for the hint :)

btw, is there a way to get an overview of all created functions (i assume pg_operator lists all operators and thus all results of CREATE OPERATOR .., where does CREATE FUNCTION .. end up?
(if i missed this in manuals somewhere please save yourself the typing and just point me ;) )

Esger

--
NeoMail - Webmail that doesn't suck... as much.
http://neomail.sourceforge.net

#6Esger Abbink
pggeneral@bumblebeast.com
In reply to: Esger Abbink (#5)
Re: oid problem with dumping database (failed sanity check, opr with oid 280515 was not found)

"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

It indeed turned out to be a stale reference. Probably the operator was dropped and reloaded without recreating all other referring operators (i guess thats the way to prevent this problem).

Thanks for the hint :)

btw, is there a way to get an overview of all created functions (i assume pg_operator lists all operators and thus all results of CREATE OPERATOR .., where does CREATE FUNCTION .. end up?
(if i missed this in manuals somewhere please save yourself the typing and just point me ;) )

Esger

--
NeoMail - Webmail that doesn't suck... as much.
http://neomail.sourceforge.net

#7Esger Abbink
pggeneral@bumblebeast.com
In reply to: Esger Abbink (#6)
Re: oid problem with dumping database (failed sanity check, opr with oid 280515 was not found)

"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

It indeed turned out to be a stale reference. Probably the operator was dropped and reloaded without recreating all other referring operators (i guess thats the way to prevent this problem).

Thanks for the hint :)

btw, is there a way to get an overview of all created functions (i assume pg_operator lists all operators and thus all results of CREATE OPERATOR .., where does CREATE FUNCTION .. end up?
(if i missed this in manuals somewhere please save yourself the typing and just point me ;) )

Esger

--
NeoMail - Webmail that doesn't suck... as much.
http://neomail.sourceforge.net

#8Esger Abbink
pggeneral@bumblebeast.com
In reply to: Esger Abbink (#7)
Re: oid problem with dumping database (failed sanity check, opr with oid 280515 was not found)

"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

It indeed turned out to be a stale reference. Probably the operator was dropped and reloaded without recreating all other referring operators (i guess thats the way to prevent this problem).

Thanks for the hint :)

btw, is there a way to get an overview of all created functions (i assume pg_operator lists all operators and thus all results of CREATE OPERATOR .., where does CREATE FUNCTION .. end up?
(if i missed this in manuals somewhere please save yourself the typing and just point me ;) )

Esger

--
NeoMail - Webmail that doesn't suck... as much.
http://neomail.sourceforge.net

#9Esger Abbink
pggeneral@bumblebeast.com
In reply to: Esger Abbink (#8)
Re: oid problem with dumping database (failed sanity check, opr with oid 280515 was not found)

"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

It indeed turned out to be a stale reference. Probably the operator was dropped and reloaded without recreating all other referring operators (i guess thats the way to prevent this problem).

Thanks for the hint :)

btw, is there a way to get an overview of all created functions (i assume pg_operator lists all operators and thus all results of CREATE OPERATOR .., where does CREATE FUNCTION .. end up?
(if i missed this in manuals somewhere please save yourself the typing and just point me ;) )

Esger

--
NeoMail - Webmail that doesn't suck... as much.
http://neomail.sourceforge.net

#10Esger Abbink
pggeneral@bumblebeast.com
In reply to: Esger Abbink (#9)
Re: oid problem with dumping database (failed sanity check, opr with oid 280515 was not found)

wtf?

i dont know what happened, my apologies.

(and i hope this one doesnt start multiplying...)

On Thu, 2002-01-17 at 10:31, Esger Abbink wrote:

NeoMail - Webmail that doesn't suck... as much.

Well it is this morning!!!

This is the 7th copy of the same mail I recieved in 5 minutes

Cheers

Tony

--
RedHat Linux on Sony Vaio C1XD/S
http://www.animaproductions.com/linux2.html
Macromedia UltraDev with PostgreSQL
http://www.animaproductions.com/ultra.html

--
NeoMail - Webmail that doesn't suck... as much.
http://neomail.sourceforge.net