Thread: ERROR: LargeObjectDrop: large object

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?

"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

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