From: | Chris Browne <cbbrowne(at)acm(dot)org> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Default autovacuum settings too conservative |
Date: | 2006-02-06 22:15:16 |
Message-ID: | 60mzh4i16z.fsf@dba2.int.libertyrms.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-performance |
matthew(at)zeut(dot)net ("Matthew T. O'Connor") writes:
> I think the default settings should be designed to minimize the
> impact autovacuum has on the system while preventing the system from
> ever getting wildly bloated (also protect xid wraparound, but that
> doesn't have anything to do with the thresholds).
That would suggest setting the "base threshold"
autovacuum_vacuum_threshold relatively low, and the "scale factor"
autovacuum_vacuum_scale_factor fairly high.
--
let name="cbbrowne" and tld="ntlug.org" in name ^ "@" ^ tld;;
http://cbbrowne.com/info/nonrdbms.html
I think it may be possible to simplify and condense the content of
this thread somewhat:
"GX is an ex-API. It is no longer supported" - The Rest of Us
"No it isn't. It's just pining for the fjords!" - Lawson
-- Michael Paquette
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-02-07 01:33:30 | Re: [HACKERS] Postgres 8.1.x and MIT Kerberos 5 |
Previous Message | Vivek Khera | 2006-02-06 20:00:12 | Re: Default autovacuum settings too conservative |
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2006-02-07 04:11:05 | Re: partitioning and locking problems |
Previous Message | Andrew Lazarus | 2006-02-06 20:36:15 | Re: execution plan : Oracle vs PostgreSQL |