From: Dan Harris <fbsd@drivefaster.net>
To: PostgreSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: [ADMIN] reclaiming disk space after major updates
Date: Fri, 08 Jun 2007 08:29:24 -0600
Message-ID: <466967C4.70606@drivefaster.net> (raw)
In-Reply-To: <20070608140354.GV17144@phlogiston.dyndns.org>
References: <46672F7C.4020400@drivefaster.net>
<20070607192025.GO14087@phlogiston.dyndns.org>
<46687820.9000604@drivefaster.net>
<20070608140354.GV17144@phlogiston.dyndns.org>
Andrew Sullivan wrote:
> On Thu, Jun 07, 2007 at 03:26:56PM -0600, Dan Harris wrote:
>> They don't always have to be in a single transaction, that's a good idea to
>> break it up and vacuum in between, I'll consider that. Thanks
>
> If you can do it this way, it helps _a lot_. I've had to do this
> sort of thing, and breaking into groups of a couple thousand or so
> really made the difference.
>
> A
>
One more point in my original post.. For my own education, why does VACUUM FULL
prevent reads to a table when running (I'm sure there's a good reason)? I can
certainly understand blocking writes, but if I could still read from it, I'd
have no problems at all!
-Dan
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-performance@postgresql.org
Cc: fbsd@drivefaster.net
Subject: Re: [ADMIN] reclaiming disk space after major updates
In-Reply-To: <466967C4.70606@drivefaster.net>
* 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