From: David Wall <dwall@Yozons.com>
To: pgsql-general@postgresql.org
To: pgsql-interfaces@postgresql.org
Subject: Re: Vacuum analyze in 7.1.1
Date: Wed, 13 Jun 2001 21:15:28 -0700
Message-ID: <019d01c0f488$a520e560$5a2b7ad8@expertrade.com> (raw)
References: <00c401c0f43b$a5423000$5a2b7ad8@expertrade.com>
<3101.992468005@sss.pgh.pa.us>
<006501c0f45b$eca1c580$5a2b7ad8@expertrade.com>
<15660.992481431@sss.pgh.pa.us>
<016901c0f486$a6372240$5a2b7ad8@expertrade.com>
> I'll have to see if JDBC does an unlink anywhere.
Whoa! Looks like JDBC (as makes sense if you think about the libraries)
doesn't unlink those large objects. There is a call in the
postgresql-specific for doing the lo_unlink, but it requires an OID, and
when deleting a row, most of the time I only know the primary key, not the
OIDs inside. So, I guess I'll have to run vacuumlo from contrib before I do
the regular vacuum.
Does anybody know if vacuumlo is truly safe to use? I just ran it on my
test system and it removed a bunch of orphans, but I just hope they were
really orphans!
David
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-interfaces@postgresql.org
Cc: dwall@Yozons.com, pgsql-general@postgresql.org
Subject: Re: Vacuum analyze in 7.1.1
In-Reply-To: <019d01c0f488$a520e560$5a2b7ad8@expertrade.com>
* 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