| From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
|---|---|
| To: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
| Cc: | pgsql-admin(at)postgresql(dot)org, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: [PERFORM] Default autovacuum settings too conservative |
| Date: | 2006-02-07 05:05:45 |
| Message-ID: | 20060207050545.GZ1240@pervasive.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-performance |
On Wed, Feb 01, 2006 at 04:37:07PM -0500, Matthew T. O'Connor wrote:
> 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).
I don't really see the logic behind that. Problems caused by inadequate
vacuuming seem to be much more prevalent than problems caused by vacuum
impacting the system. If vacuum impact is a concern I think it more
reasonable to make the default vacuum_cost_delay non-zero instead.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Browne | 2006-02-07 06:14:53 | Re: Default autovacuum settings too conservative |
| Previous Message | Bruce Momjian | 2006-02-07 01:33:30 | Re: [HACKERS] Postgres 8.1.x and MIT Kerberos 5 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2006-02-07 05:06:26 | Re: pgbench output |
| Previous Message | Jim C. Nasby | 2006-02-07 04:11:05 | Re: partitioning and locking problems |