pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Goldner <MGoldner@agmednet.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Testing lo_unlink() in psql
Date: Wed, 03 Oct 2007 12:25:06 -0400
Message-ID: <25835.1191428706@sss.pgh.pa.us> (raw)
In-Reply-To: <1191426756.10212.20.camel@mgoldner-desktop>
References: <1191426756.10212.20.camel@mgoldner-desktop>

"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



view thread (2+ messages)

Message-ID: <25835.1191428706@sss.pgh.pa.us>
Permalink:  ../25835.1191428706@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/25835.1191428706@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, MGoldner@agmednet.com
  Subject: Re: Testing lo_unlink() in psql
  In-Reply-To: <25835.1191428706@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox