| From: | Pandurangan R S <pandurangan(dot)r(dot)s(at)gmail(dot)com> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | Michael Riess <mlriess(at)gmx(dot)de>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Autovacuum / full vacuum |
| Date: | 2006-01-17 11:35:20 |
| Message-ID: | 5e744e3d0601170335v1b367766l4f9297526c52b084@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
>> You should never have to do full vacuums...
I would rather say, You should never have to do full vacuums by any
periodic means. It may be done on a adhoc basis, when you have figured
out that your table is never going to grow that big again.
On 1/17/06, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> wrote:
> > So my question is: What's the use of an autovacuum daemon if I still
> > have to use a cron job to do full vacuums? wouldn't it just be a minor
> > job to enhance autovacuum to be able to perform full vacuums, if one
> > really wants it to do that - even if some developers think that it's the
> > wrong approach?
>
> You should never have to do full vacuums...
>
> Chris
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Stone | 2006-01-17 12:08:05 | Re: Autovacuum / full vacuum |
| Previous Message | Michael Riess | 2006-01-17 10:33:02 | Re: Autovacuum / full vacuum |