Re: ERROR: LargeObjectDrop: large object

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Thomas T(dot) Thai" <tom(at)minnesota(dot)com>
Cc: PostgreSQL General <pgsql-general(at)postgresql(dot)org>
Subject: Re: ERROR: LargeObjectDrop: large object
Date: 2002-11-08 14:48:57
Message-ID: 5593.1036766937@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Thomas T. Thai" <tom(at)minnesota(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Andreas 2002-11-08 14:53:22 Need hints on distributed DB
Previous Message Robert Treat 2002-11-08 14:39:30 Re: OT: mailing list delays