Re: OID type creates files that don't go away - Mailing list pgsql-admin

From Stephan Szabo
Subject Re: OID type creates files that don't go away
Date
Msg-id Pine.BSF.4.21.0101241023140.57647-100000@megazone23.bigpanda.com
Whole thread Raw
In response to OID type creates files that don't go away  ("David Wall" <d.wall@computer.org>)
List pgsql-admin
I'm guessing you're using the Large Object interface?  AFAIR, The LO
interface doesn't automatically clean up after you so you have to make
triggers as necessary to deal with deletes.

On Tue, 23 Jan 2001, David Wall wrote:

> I've created several blobs using the OID type.  I note that the database
> stores the "oid" number that represents two files on disk, such as xinv21281
> and xinx21281 with the oid in the database showing up as 21281 via a SELECT.
>
> But, I deleted a row that contained this oid, and the two 'x' files are
> still on disk.  I then ran a VACUUM, saw that 1 record was reaped, but the
> two 'x' files remain.  Are these 'x' files going to be reused in some
> manner, or is this a bug that keeps them around despite the fact that the
> database row for it has been removed?


pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: forgotten data base superuser password
Next
From: Dirk Heinrichs
Date:
Subject: Some thoughts on replication