Skip site navigation (1) Skip section navigation (2)

autovacuum strategy / parameters

From: Rick <richard(dot)branton(at)ca(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: autovacuum strategy / parameters
Date: 2010-04-21 15:06:11
Message-ID: c2d2b6cf-895f-4a4b-aa8b-3adaac33c794@z3g2000yqz.googlegroups.com (view raw or flat)
Thread:
Lists: pgsql-performance
I have a DB with small and large tables that can go up to 15G.
For performance benefits, it appears that analyze has much less cost
than vacuum, but the same benefits?
I can’t find any clear recommendations for frequencies and am
considering these parameters:

Autovacuum_vacuum_threshold = 50000
Autovacuum_analyze_threshold = 10000
Autovacuum_vacuum_scale_factor = 0.01
Autovacuum_analyze_scale_factor = 0.005

This appears it will result in table analyzes occurring around 10,000
to 85,000 dead tuples and vacuum occuring around 50,000 to 200,000,
depending on the table sizes.

Can anyone comment on whether this is the right strategy and targets
to use?

Responses

pgsql-performance by date

Next:From: Nikolas EverettDate: 2010-04-21 15:07:11
Subject: Re: SOLVED ... Re: Getting rid of a cursor from JDBC .... Re: [PERFORM] Re: HELP: How to tame the 8.3.x JDBC driver with a biq guery result set
Previous:From: Robert HaasDate: 2010-04-21 14:41:25
Subject: Re: SOLVED ... Re: Getting rid of a cursor from JDBC .... Re: [PERFORM] Re: HELP: How to tame the 8.3.x JDBC driver with a biq guery result set

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group