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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
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?
From | Date | Subject | |
---|---|---|---|
Next Message | Nikolas Everett | 2010-04-21 15:07:11 | 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 Message | Robert Haas | 2010-04-21 14:41:25 | 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 |