Re: [BUGS] can't vacuum LargeObjects now - Mailing list pgsql-interfaces

From Peter T Mount
Subject Re: [BUGS] can't vacuum LargeObjects now
Date
Msg-id Pine.LNX.3.95.980429181845.6145A-100000@retep.org.uk
Whole thread Raw
List pgsql-interfaces
[cc'd to interfaces]

On Tue, 28 Apr 1998, Park, Chul-Su wrote:

> Hi,
>
> When I try to "vacuum" a db there was some messages:
>
> mydb=>vacuum;
> ...
> NOTICE:  Rel xinv169971: can't vacuum LargeObjects now
> ...
> VACUUM
>
> this seems to be
> (0) I deleted some rows in the TABLE containing oids as a field
> (1) those large objects seems to be orphaned.
>
> then how can I remove unused LargeObjects?  And when will it be possible
> dump/restore large objects?(I mean upgrade existing dbs keeping oids).

I can't remember vacuum ever removing an orphaned large object, just
cleaning up any deleted space within the objects.

There is currently no way for the system to remove orphaned large objects
- it's up to the dba or the client application.

There was a discussion about handling orphaned large objects as this is a
problem for both the JDBC & ODBC drivers.

One of the things on my list for JDBC 6.4 is solving (or a solution to)
orphaned large objects.


--
Peter T Mount  peter@retep.org.uk or petermount@earthling.net
Main Homepage: http://www.demon.co.uk/finder (moving soon to www.retep.org.uk)
************ Someday I may rebuild this signature completely ;-) ************
Work Homepage: http://www.maidstone.gov.uk Work EMail: peter@maidstone.gov.uk


pgsql-interfaces by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Revised proposal for libpq and FE/BE protocol changes
Next
From: "Ken J. Wright"
Date:
Subject: 16 bit driver?