Re: autovacuum for large periodic deletes

From: "Sriram Dandapani" <sdandapani(at)counterpane(dot)com>
To: "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>
Cc: <pgsql-admin(at)postgresql(dot)org>
Subject: Re: autovacuum for large periodic deletes
Date: 2006-05-17 20:39:35
Message-ID: 6992E470F12A444BB787B5C937B9D4DF045AF177@ca-mail1.cis.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

About 5-10 million rows stay after deletion. There are a few other
tables where the daily deletion totals about 3-6 million.

Would a vacuum full/cluster affect other operations. These tables have a
24x7 high data insertion rate.

-----Original Message-----
From: Alvaro Herrera [mailto:alvherre(at)commandprompt(dot)com]
Sent: Wednesday, May 17, 2006 1:36 PM
To: Sriram Dandapani
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] autovacuum for large periodic deletes

Sriram Dandapani wrote:

> Every night, a delete of about 50 million rows occurs on a table. Do
we
> need to explicitly vacuum the table or will autovacuum handle the
large
> deletes without affecting performance. I am trying to determine
whether
> or not I should completely rely on autovacuum or also tinker with
manual
> vacuums.

How many rows stay in the table after the massive deletion? It may be
that it's best for you to issue a CLUSTER or VACUUM FULL instead of
VACUUM. (In any case, autovacuum would vacuum the table eventually, but
maybe you can do better.)

--
Alvaro Herrera
http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Chris Browne 2006-05-17 20:56:06 Re: autovacuum for large periodic deletes
Previous Message Alvaro Herrera 2006-05-17 20:36:21 Re: autovacuum for large periodic deletes