Re: Is vacuum full lock like old's vacuum's lock? - Mailing list pgsql-general

From Francisco Reyes
Subject Re: Is vacuum full lock like old's vacuum's lock?
Date
Msg-id 20020308152829.W26200-100000@zoraida.natserv.net
Whole thread Raw
In response to Re: Is vacuum full lock like old's vacuum's lock?  ("Gregory Wood" <gregw@com-stock.com>)
List pgsql-general
On Fri, 8 Mar 2002, Gregory Wood wrote:

> > Do sequential scans go over the entire space, including the space not in
> > use? It would be great if there was some kind of optimization that could
> > move the empty space towards the end. It would probably be an expensive
> > operation, but it may be very helpfull on databases with a big turnaround.
>
> The only difference between doing that and doing a VACUUM FULL would be that
> the disk usage would remain the same.

There is one other extremely important difference. VACUUM FULL locks the
table/database.


> Personally, I would continue do the entire database once a week, and select
> a few key tables that have a lot of UPDATEs/DELETEs to do daily

thanks like a reasonable thing to do.


pgsql-general by date:

Previous
From: Joel Burton
Date:
Subject: Re: Conditional constraint?
Next
From: "Gregory Wood"
Date:
Subject: Re: Is vacuum full lock like old's vacuum's lock?