| From: | Francisco Reyes <lists(at)natserv(dot)com> |
|---|---|
| To: | Gregory Wood <gregw(at)com-stock(dot)com> |
| Cc: | PostgreSQL-General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Is vacuum full lock like old's vacuum's lock? |
| Date: | 2002-03-08 20:30:36 |
| Message-ID: | 20020308152829.W26200-100000@zoraida.natserv.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Wood | 2002-03-08 20:46:11 | Re: Is vacuum full lock like old's vacuum's lock? |
| Previous Message | Joel Burton | 2002-03-08 19:44:10 | Re: Conditional constraint? |