Re: Plans for solving the VACUUM problem

From: mlw <markw(at)mohawksoft(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Plans for solving the VACUUM problem
Date: 2001-05-18 01:31:59
Message-ID: 3B047B8F.7406CC14@mohawksoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
>
I love it all.
I agree that vacuum should be an optional function that really packs tables.

I also like the idea of a vacuum that runs in the background and does not too
badly affect operation.

My only suggestion would be to store some information in the statistics about
whether or not, and how bad, a table needs to be vacuumed. In a scheduled
background environment, the tables that need it most should get it most often.
Often times many tables never need to be vacuumed.

Also, it would be good to be able to update the statistics without doing a
vacuum, i.e. rather than having to vacuum to analyze, being able to analyze
without a vacuum.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2001-05-18 02:27:51 Re: Plans for solving the VACUUM problem
Previous Message Alex Pilosov 2001-05-18 00:58:11 operators and indices?