From: Michael Goldner <MGoldner@agmednet.com>
To: pgsql-admin@postgresql.org
Subject: Testing lo_unlink() in psql
Date: Wed, 3 Oct 2007 11:52:36 -0400
Message-ID: <1191426756.10212.20.camel@mgoldner-desktop> (raw)
I'm running postgres 8.1.8 on redhat.
I have a very large table that contains an OID that refers to a large
object. I have a rule defined that calls lo_unlink() on a delete. I
seem to get a successful return status on the delete, but my total disk
space used does not seem to shrink.
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()?
Is there some other reason I'm not reclaiming disk space after an
lo_unlink()?
Also, is there any way to determine the actual filename that the OID
references? I'd like to be able to do an "ls -l <filename>" before and
after the lo_unlink() command to confirm that the file has been removed.
I can't really do lo_list from psql because the table is > 2.5 million
rows.
Thanks,
Mike
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: MGoldner@agmednet.com
Subject: Re: Testing lo_unlink() in psql
In-Reply-To: <1191426756.10212.20.camel@mgoldner-desktop>
* 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