| From: | "Jim C(dot) Nasby" <jimn(at)enterprisedb(dot)com> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | Tom Dunstan <tom(at)tomd(dot)cc>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Mid cycle release? |
| Date: | 2006-09-17 00:15:23 |
| Message-ID: | 20060917001522.GK38854@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Sep 14, 2006 at 02:36:22PM -0700, Joshua D. Drake wrote:
> But on a serious note, the problem I run into is exactly the opposite.
> Someone will turn on autovacuum because they thought it was a good idea
> and for their work load, it isn't. So instead of creating new and
> interesting ways to allow their database to be more efficient, I am
> dealing with snafu's created by my own community.
Then we should change autovacuum so that it stays out of the way when
tables are being vacuumed frequently enough via an external means.
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2006-09-17 00:28:24 | Re: Mid cycle release? |
| Previous Message | Joshua D. Drake | 2006-09-17 00:02:40 | Re: [HACKERS] Developer's Wiki |