From: Tom Lane <tgl@sss.pgh.pa.us>
To: Achilleus Mantzios <achill@matrix.gatewaynet.com>
Cc: David Durst <ddurst@larubber.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Scheduling Events?
Date: Fri, 24 Jan 2003 10:32:16 -0500
Message-ID: <13296.1043422336@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.LNX.4.44.0301241150460.12585-100000@matrix.gatewaynet.com>
References: <Pine.LNX.4.44.0301241150460.12585-100000@matrix.gatewaynet.com>
Achilleus Mantzios <achill@matrix.gatewaynet.com> writes:
> On Fri, 24 Jan 2003, David Durst wrote:
>> Here is the basic problem w/ using CRON in an accounting situation.
>>
>> I can't be sure that cron will always be up when the DB is up,
>> so lets say crond goes down for some random reason (User, System error,
>> Etc..)
> I you cannot depend on your system to run crond
> then you should not depend on it to run postgresql either.
Indeed. Cron is one of the oldest and most basic Unix daemons.
I find it really, really, really hard to believe that any substitute
code that anyone might come up with is going to be more reliable than
cron.
If it makes you feel better, you could institute some cross-checking.
For example, have the cron-launched task update a timestamp in some
database table whenever it finishes. Then make your user applications
check that timestamp when they start up (or every so often) and complain
if it's not within the range (now - expected cron frequency, now).
That doesn't fix the problem, but at least makes some humans aware of it.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, achill@matrix.gatewaynet.com, ddurst@larubber.com
Subject: Re: Scheduling Events?
In-Reply-To: <13296.1043422336@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox