From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kevin Kempter <kevin@kevinkempterllc.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: large objects & space usage
Date: Sun, 13 Jan 2008 16:04:25 -0500
Message-ID: <8811.1200258265@sss.pgh.pa.us> (raw)
In-Reply-To: <200801131301.04468.kevin@kevinkempterllc.com>
References: <200801131301.04468.kevin@kevinkempterllc.com>
Kevin Kempter <kevin@kevinkempterllc.com> writes:
> 3) we did a pg_dump and a reload into a database on the test box and the table
> is still 30Gig.
You need to find out *exactly* what they did there.
The idea that comes to mind is that they dropped and reloaded the table
itself, but didn't do anything about cleaning out pg_largeobject, and
when they say "the table is still 30Gig" they actually mean the whole
database directory is still 30Gig.
If there are no other tables storing large objects in the database,
dropping and reloading the whole database is probably the simplest
solution. Otherwise they're going to need to make sure the unwanted
LOs have been cleaned out (see contrib/vacuumlo) and then do a VACUUM
FULL or similar on pg_largeobject.
regards, tom lane
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, kevin@kevinkempterllc.com
Subject: Re: large objects & space usage
In-Reply-To: <8811.1200258265@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