ERROR: LargeObjectDrop: large object

Started by Thomas T. Thaiover 23 years ago3 messagesgeneral
Jump to latest
#1Thomas T. Thai
tom@minnesota.com

I just upgraded from 7.2 to 7.2.3 and noticed these two errors:

ERROR: LargeObjectDrop: large object 9313937 not found
ERROR: LargeObjectDrop: large object 9313938 not found

Is this something to be concerned about?

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Thomas T. Thai (#1)
Re: ERROR: LargeObjectDrop: large object

"Thomas T. Thai" <tom@minnesota.com> writes:

I just upgraded from 7.2 to 7.2.3 and noticed these two errors:
ERROR: LargeObjectDrop: large object 9313937 not found
ERROR: LargeObjectDrop: large object 9313938 not found
Is this something to be concerned about?

You tell us. All that message says is something called lo_unlink()
with a parameter that's not the OID of any extant large object. If
you have application code that's in the habit of doing such things,
then it isn't a problem; otherwise, it might be an indicator that
you've got bad data or who knows what...

FWIW, I doubt that the version update has anything to do with it.

regards, tom lane

#3Robert Treat
xzilla@users.sourceforge.net
In reply to: Tom Lane (#2)
Re: ERROR: LargeObjectDrop: large object

On Fri, 2002-11-08 at 09:48, Tom Lane wrote:

"Thomas T. Thai" <tom@minnesota.com> writes:

I just upgraded from 7.2 to 7.2.3 and noticed these two errors:
ERROR: LargeObjectDrop: large object 9313937 not found
ERROR: LargeObjectDrop: large object 9313938 not found
Is this something to be concerned about?

You tell us. All that message says is something called lo_unlink()
with a parameter that's not the OID of any extant large object. If
you have application code that's in the habit of doing such things,
then it isn't a problem; otherwise, it might be an indicator that
you've got bad data or who knows what...

FWIW, I doubt that the version update has anything to do with it.

If he did a dump/restore, might it be possible he didn't properly
transfer the large objects?

Robert Treat