From: Alvaro Herrera <alvherre@commandprompt.com>
To: Sriram Dandapani <sdandapani@counterpane.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: autovacuum for large periodic deletes
Date: Wed, 17 May 2006 16:36:21 -0400
Message-ID: <20060517203621.GR26367@surnet.cl> (raw)
In-Reply-To: <6992E470F12A444BB787B5C937B9D4DF045AF151@ca-mail1.cis.local>
References: <6992E470F12A444BB787B5C937B9D4DF045AF151@ca-mail1.cis.local>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: alvherre@commandprompt.com, sdandapani@counterpane.com
Subject: Re: autovacuum for large periodic deletes
In-Reply-To: <20060517203621.GR26367@surnet.cl>
References: <6992E470F12A444BB787B5C937B9D4DF045AF151@ca-mail1.cis.local> <20060517203621.GR26367@surnet.cl>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox