Re: Testing lo_unlink() in psql - Mailing list pgsql-admin

From Tom Lane
Subject Re: Testing lo_unlink() in psql
Date
Msg-id 25835.1191428706@sss.pgh.pa.us
Whole thread Raw
In response to Testing lo_unlink() in psql  ("Michael Goldner" <MGoldner@agmednet.com>)
List pgsql-admin
"Michael Goldner" <MGoldner@agmednet.com> writes:
> I've run "VACUUM ANALYZE" on the table after the delete and have the
> same behavior.  Do I need to run a "VACUUM FULL" to get the space back
> after an lo_unlink()?

Vacuuming the table isn't gonna help much, because all that reclaims
is your table row, not the space occupied by the large object.  Large
objects live in pg_largeobject, and you need to be vacuuming *that*
on a regular basis if you do much deleting or updating of large objects.

> Also, is there any way to determine the actual filename that the OID
> references?

You appear to be seriously confused about how large objects are
stored.  See
http://www.postgresql.org/docs/8.1/static/largeobjects.html
http://www.postgresql.org/docs/8.1/static/catalog-pg-largeobject.html

            regards, tom lane

pgsql-admin by date:

Previous
From: "Michael Goldner"
Date:
Subject: Testing lo_unlink() in psql
Next
From: Devrim GÜNDÜZ
Date:
Subject: Re: Database Migration