From: Markus Schaber <schabios@logi-track.com>
To: Gaetano Mendola <mendola@bigfoot.com>
Cc: Matthew T. O'Connor <matthew@zeut.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: is pg_autovacuum so effective ?
Date: Thu, 24 Feb 2005 13:13:09 +0100
Message-ID: <421DC4D5.1070909@logi-track.com> (raw)
In-Reply-To: <421DB36B.70004@bigfoot.com>
References: <cvg29i$2l69$1@news.hub.org>
<12400.1109107683@sss.pgh.pa.us>
<421BD64E.30803@bigfoot.com>
<60psyr265t.fsf@dba2.int.libertyrms.com>
<421CD6F0.8010406@zeut.net>
<421DB36B.70004@bigfoot.com>
Hi, Gaetano,
Gaetano Mendola schrieb:
> I have the same requirement too. Actually pg_autovacuum can not be
> instructed "per table" so some time the global settings are not good
> enough. I have a table of logs with 6 milions rows ( 3 years logs )
> I insert on that page ~ 6000 rows for day. I'm running pg_autovacuum
> with setting to ANALYZE or VACUUM table if the 10% is touched.
> With this setting pg_autovacuum will analyze that table each 3 months!!!
If you have only inserts, and only so few on a large table, you do not
need to vacuum such often. Not to reclaim space, only to prevent
transaction ID wraparound (which is ensured by pg_autovacuum).
And if the data distribution does not change, frequently calling ANALYZE
does not help much, either.
Markus
--
markus schaber | dipl. informatiker
logi-track ag | rennweg 14-16 | ch 8001 zürich
phone +41-43-888 62 52 | fax +41-43-888 62 53
mailto:schabios@logi-track.com | www.logi-track.com
Attachments:
signature.asc (application/pgp-signature, 255B) download
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: schabios@logi-track.com, mendola@bigfoot.com, matthew@zeut.net
Subject: Re: is pg_autovacuum so effective ?
In-Reply-To: <421DC4D5.1070909@logi-track.com>
* 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