Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 792AA9F9C55 for ; Wed, 3 Oct 2007 13:25:14 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 82798-05 for ; Wed, 3 Oct 2007 13:25:07 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 526FB9F9A55 for ; Wed, 3 Oct 2007 13:25:08 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l93GP6BR025836; Wed, 3 Oct 2007 12:25:06 -0400 (EDT) To: "Michael Goldner" cc: pgsql-admin@postgresql.org Subject: Re: Testing lo_unlink() in psql In-reply-to: <1191426756.10212.20.camel@mgoldner-desktop> References: <1191426756.10212.20.camel@mgoldner-desktop> Comments: In-reply-to "Michael Goldner" message dated "Wed, 03 Oct 2007 11:52:36 -0400" Date: Wed, 03 Oct 2007 12:25:06 -0400 Message-ID: <25835.1191428706@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/14 X-Sequence-Number: 26928 "Michael Goldner" 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