From: Tom Lane <tgl@sss.pgh.pa.us>
To: Neuber, Dirk <dirk.neuber@barco.com>
Cc: Guillaume Lelarge <guillaume@lelarge.info>
Cc: Henry, Frank <frank.henry@barco.com>
Cc: pgsql-admin@postgresql.org, "Scott Marlowe" <scott.marlowe@gmail.com>
Subject: Re: Large files in main/base
Date: Sun, 11 Jul 2010 11:51:00 -0400
Message-ID: <19574.1278863460@sss.pgh.pa.us> (raw)
In-Reply-To: <ED2EA636E2C9744A96B417491D4793BB07E00D7A@KUUMEX03.barco.com>
References: <ED2EA636E2C9744A96B417491D4793BB07E00D3D@KUUMEX03.barco.com>
<4C38605A.3010101@lelarge.info>
<15568.1278773686@sss.pgh.pa.us>
<ED2EA636E2C9744A96B417491D4793BB07E00D7A@KUUMEX03.barco.com>
"Neuber, Dirk" <dirk.neuber@barco.com> writes:
> One last question. After using vacuumlo the file size of 16385/2613 is
> still the same as before.
> It seems the content has been removed but the file itself hasn't been
> compacted.
> Is there an option or tool which can do this as well ?
Yeah, you still need to apply VACUUM FULL to bring the physical file
size down. (Ordinary VACUUM mostly just recycles space within the
file --- it can truncate the file if the end pages are empty, but
it won't move data around to make that possible.)
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, dirk.neuber@barco.com, guillaume@lelarge.info, frank.henry@barco.com, scott.marlowe@gmail.com
Subject: Re: Large files in main/base
In-Reply-To: <19574.1278863460@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