From: | Dan Harris <fbsd(at)drivefaster(dot)net> |
---|---|
To: | PostgreSQL Performance <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: [ADMIN] reclaiming disk space after major updates |
Date: | 2007-06-08 14:29:24 |
Message-ID: | 466967C4.70606@drivefaster.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-performance |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Sullivan | 2007-06-08 15:10:57 | Re: [ADMIN] reclaiming disk space after major updates |
Previous Message | Andrew Sullivan | 2007-06-08 14:20:30 | Re: the right time to vacuum database? |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Sullivan | 2007-06-08 15:10:57 | Re: [ADMIN] reclaiming disk space after major updates |
Previous Message | Andrew Sullivan | 2007-06-08 14:03:54 | Re: reclaiming disk space after major updates |