Skip site navigation (1) Skip section navigation (2)

Re: large objects & space usage

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kevin Kempter <kevin(at)kevinkempterllc(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: large objects & space usage
Date: 2008-01-13 21:04:25
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
Kevin Kempter <kevin(at)kevinkempterllc(dot)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

In response to


pgsql-admin by date

Next:From: Vishal MailinglistDate: 2008-01-13 22:13:40
Subject: Re: Need some info.
Previous:From: Milen A. RadevDate: 2008-01-13 20:12:10
Subject: Re: large objects & space usage

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group