pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Gaetano Mendola <mendola@bigfoot.com>
To: Matthew T. O'Connor <matthew@zeut.net>
Subject: Re: pg_autovacuum parameters
Date: Tue, 03 Aug 2004 17:54:44 +0200
Message-ID: <410FB544.1010403@bigfoot.com> (raw)
In-Reply-To: <410F9EF4.1070003@zeut.net>
References: <A177ACC01D78D4118FC100508BAE3F7AF653BB@TELECOMMAIL>
	<410F9EF4.1070003@zeut.net>

Matthew T. O'Connor wrote:

> Lending, Rune wrote:
> 
>> Hello all.
>>  
>> I am managing a large database with lots of transactions in different 
>> tables.
>> The largest tables have around 5-6 millions tuples and around 
>> 50000-60000 inserts and maybe 20000 updates pr day.
>> While the smalest tables have only a few tuples and a few updates 
>> /inserts pr day. In addition we have small tables with many 
>> updates/inserts. So what I am saying is that there is all kinds of 
>> tables and uses of tables in our database.
>> This, I think, makes it difficult to set up pg_autovacuum. I am now 
>> running vacuum jobs on different tables in cron.
>>  
>> What things should I consider when setting but base and threshold 
>> values in pg_autovacuum? Since the running of vacuum and analyze is 
>> relative to the table size, as it must be, I think it is difficult to 
>> cover all tables..
> 
> 
> One of the biggest problems with the version of pg_autovacuum in 7.4 
> contrib is that you can only specify one set of thresholds, which often 
> isn't flexible enough.  That said the thresholds are based on table 
> since since you specify both a base value and a scaling factor so 
> pg_autovacuum -v 1000 -V 1 will vacuum a table with 100 rows every 200 
> updates, but will vacuum a table with 1,000,000 rows every 1,000,100 
> updates.
> 
>> Are there anyone who have some thoughts around this?
> 
> 
> Basically, you should be able to use pg_autovacuum to do most of the 
> vacuuming, if there are a few tables that aren't getting vacuumed often 
> enough, then you can add a vacuum command to cron for those specific 
> tables.

And in the version 7.5^H^H^H8.0 ( Tom Lane docet :-) ) I think is possible
specify that thresholds per table...


Regards
Gateano Mendola







view thread (3+ messages)

Message-ID: <410FB544.1010403@bigfoot.com>
Permalink:  ../410FB544.1010403@bigfoot.com/
Also on:    postgresql.org/message-id/410FB544.1010403@bigfoot.com

 · 

reply

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: mendola@bigfoot.com, matthew@zeut.net
  Subject: Re: pg_autovacuum parameters
  In-Reply-To: <410FB544.1010403@bigfoot.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