Thread: oid problem with dumping database (failed sanity check, opr with oid 280515 was not found)
oid problem with dumping database (failed sanity check, opr with oid 280515 was not found)
From
"Esger Abbink"
Date:
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
Re: oid problem with dumping database (failed sanity check, opr with oid 280515 was not found)
From
Tom Lane
Date:
"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
Re: oid problem with dumping database (failed sanity check, opr with oid 280515 was not found)
From
"Esger Abbink"
Date:
> "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 otherreferring 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 resultsof 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
Re: oid problem with dumping database (failed sanity check, opr with oid 280515 was not found)
From
"Esger Abbink"
Date:
> "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 otherreferring 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 resultsof 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
Re: oid problem with dumping database (failed sanity check, opr with oid 280515 was not found)
From
"Esger Abbink"
Date:
> "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 otherreferring 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 resultsof 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
Re: oid problem with dumping database (failed sanity check, opr with oid 280515 was not found)
From
"Esger Abbink"
Date:
> "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 otherreferring 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 resultsof 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
Re: oid problem with dumping database (failed sanity check, opr with oid 280515 was not found)
From
"Esger Abbink"
Date:
> "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 otherreferring 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 resultsof 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
Re: oid problem with dumping database (failed sanity check, opr with oid 280515 was not found)
From
"Esger Abbink"
Date:
> "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 otherreferring 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 resultsof 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
Re: oid problem with dumping database (failed sanity check, opr with oid 280515 was not found)
From
"Esger Abbink"
Date:
> "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 otherreferring 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 resultsof 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
Re: oid problem with dumping database (failed sanity check, opr with oid 280515 was not found)
From
"Esger Abbink"
Date:
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