Re: new GUC var: autovacuum_process_all_tables

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-06 15:06:16
Message-ID: 498C51E8.1040402@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Simon Riggs wrote:
> All I'm saying is *if* we put scheduling inside Postgres for autovacuum
> *then* we should make it general purpose scheduling.
>
> If anybody uses the argument that "we have external schedulers, so don't
> put them in the database" then that argument applies equally to
> scheduling autovacuum. It's easy to turn autovacuum on/off via an
> external scheduler, yet look upthread and see how many people think it
> should be in the database.
>
> Whichever way you think the decision should go, the same arguments apply
> to scheduling autovacuum and scheduling other database maintenance
> tasks.
>
>

OK, I agree with that.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2009-02-06 15:39:34 Re: confirm timezone changes for new releases was Fwd: Re: [pgsql-slavestothewww] New News Entry (id: 1055)
Previous Message Robert Treat 2009-02-06 14:29:54 confirm timezone changes for new releases was Fwd: Re: [pgsql-slavestothewww] New News Entry (id: 1055)