| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: new GUC var: autovacuum_process_all_tables |
| Date: | 2009-02-05 22:29:45 |
| Message-ID: | 1233872985.26415.54.camel@jd-laptop.pragmaticzealot.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2009-02-05 at 17:08 -0500, Tom Lane wrote:
> I disagree; adding every frammish anyone could ever think of is not
> an overall improvement to the system.
>
:)
> My feeling is that we should be trying to eliminate use-cases for
> cron-driven vacuuming, not trying to make sure that cron-driven
> scripts can do anything autovacuum can.
Agreed. IMO, the user should only have to think about "vacuum" in an
abstract sense. With the exception being those "few" tables that need
the customized configuration (thus reloptions).
>
> The main remaining use-case seems to me to make vacuuming work adhere
> to some business-determined schedule, hence maintenance windows seem
> like the next thing to do.
>
Also agreed.
Sincerely,
Joshua D. Drake
> regards, tom lane
>
--
PostgreSQL - XMPP: jdrake(at)jabber(dot)postgresql(dot)org
Consulting, Development, Support, Training
503-667-4564 - http://www.commandprompt.com/
The PostgreSQL Company, serving since 1997
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2009-02-05 22:57:10 | Re: new GUC var: autovacuum_process_all_tables |
| Previous Message | Simon Riggs | 2009-02-05 22:12:49 | Re: new GUC var: autovacuum_process_all_tables |