| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Lincoln Yeoh" <lyeoh(at)pop(dot)jaring(dot)my>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | RE: Re: [GENERAL] Vacuum and Transactions |
| Date: | 2001-07-09 01:46:40 |
| Message-ID: | ECEHIKNFIMMECLEBJFIGMEDGCBAA.chriskl@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
> That might happen eventually, but I'm not all that eager to convert
> the postmaster into a (half-baked) substitute for cron. My experience
> as a dbadmin is that you need various sorts of routinely-run maintenance
> tasks anyway; VACUUM is only one of them. So you're gonna need some
> cron tasks no matter what. If we try to make the postmaster responsible
> for this sort of thing, we're going to end up reimplementing cron.
> I think that's a waste of effort.
Except that you can only set cron jobs to run every hour, etc. The DBA
might want to set it to run after say 5% of the rows in a table are
updated/deleted, etc. It is an esoteric feature, I know, but it'd be cool.
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Clift | 2001-07-09 04:30:04 | QUERY - Including the new LDP PostgreSQL HOWTO in the main PostgreSQL distribution |
| Previous Message | Tom Lane | 2001-07-09 01:46:37 | Re: Re: [GENERAL] Vacuum and Transactions |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2001-07-09 01:49:03 | RE: ADD CONSTRAINT behaviour question |
| Previous Message | Tom Lane | 2001-07-09 01:46:37 | Re: Re: [GENERAL] Vacuum and Transactions |