| 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 00:23:29 |
| Message-ID: | 498B8301.8090909@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Simon Riggs wrote:
>> not trying to make sure that cron-driven
>> scripts can do anything autovacuum can.
>>
>
> I'm not in favour of limiting our capability to internal actions only.
> If we add a capability for scheduling work, we can easily make it
> capable of scheduling many kinds of work.
>
> Writing an application maintenance utility in PL/pgSQL is much better
> than having to write it for all the different servers an application may
> need to run on. We can't ignore that many people use Windows.
>
>
I'm not sure what you're saying here. Windows has a scheduler (in my
setup, that's how my buildfarm members run). And there are third party
cron utilities as well.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mykola Stryebkov | 2009-02-06 00:49:48 | create database warning |
| Previous Message | Robert Haas | 2009-02-06 00:13:17 | Re: new GUC var: autovacuum_process_all_tables |