From: | "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Zlatko Michailov <zmichailov(at)yahoo(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Scheduled jobs |
Date: | 2003-05-12 22:38:59 |
Message-ID: | Pine.LNX.4.21.0305122331190.24875-100000@ponder.fairway2k.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 12 May 2003, Tom Lane wrote:
> "Nigel J. Andrews" <nandrews(at)investsystems(dot)co(dot)uk> writes:
> > Only cron can't handle some of those cases listed, but then one could always
> > patch one's own local installation of pg_ctl etc. to run things at startup and
> > shutdown.
>
> If you are using a typical init script setup, it's easy to add
> additional operations to the init script's start and stop actions.
>
> I'm a tad suspicious of adding on-shutdown actions anyway, as there's
> little guarantee they would get done (consider system crash, postmaster
> crash, etc).
>
> regards, tom lane
Absolutely. That's why you'd patch your startup/shutdown scripts. Adding it to
pg_ctl does enable those to kick the necessary stuff without requiring use of
the system's init scripts for manual control of the postmaster. When the
emphasis on the 'controlled' aspect of this is acknowledged then it's just a
toss up between editing pg_ctl or your own wrapper for it. I would go for my
own wrapper since then that still leaves the ability for pg_ctl to be used
_without_ kicking those startup/shutdown actions.
I believe this has arisen several times and each time there's been no
enthusiasm to stick cron into the core which I think is a reasonable stance.
--
Nigel J. Andrews
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2003-05-12 22:46:39 | Re: How are null's stored? |
Previous Message | Christopher Browne | 2003-05-12 22:38:14 | Re: Scheduled jobs |