pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: David Durst <ddurst@larubber.com>
To: pgsql-sql@postgresql.org
Subject: Re: Scheduling Events?
Date: Fri, 24 Jan 2003 00:45:38 -0800 (PST)
Message-ID: <41705.216.86.192.34.1043397938.squirrel@www.la-rubber.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0301240913220.11997-100000@matrix.gatewaynet.com>
References: <39409.216.86.192.34.1043367412.squirrel@www.la-rubber.com>
	<Pine.LNX.4.44.0301240913220.11997-100000@matrix.gatewaynet.com>

> On Thu, 23 Jan 2003, David Durst wrote:
>
>> Is there anyway to schedule DB Events based on time?
>
> Yes! cron
>
>> So lets say I had a table w/ depreciation schedules in it,
>> I would like the DB to apply the formula and make the entries on the
>> END of every month.
> On Thu, 23 Jan 2003, David Durst wrote:
>
>> Is there anyway to schedule DB Events based on time?
>
> Yes! cron
>
>> So lets say I had a table w/ depreciation schedules in it,
>> I would like the DB to apply the formula and make the entries on the
>> END of every month.

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..)

And outside adjustment is made to lets say the equipment account and that
adjustment was made on the value of the equipment, BUT it hadn't been
depreciated because crond went down and no one notice.

Now I have a HUGE issue!

So I have to be sure that all entries/adjustments are made accurately in
the time frame they were meant to happen in.





view thread (13+ messages)  latest in thread

Message-ID: <41705.216.86.192.34.1043397938.squirrel@www.la-rubber.com>
Permalink:  ../41705.216.86.192.34.1043397938.squirrel@www.la-rubber.com/
Also on:    postgresql.org/message-id/41705.216.86.192.34.1043397938.squirrel@www.la-rubber.com

 · 

reply

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: ddurst@larubber.com
  Subject: Re: Scheduling Events?
  In-Reply-To: <41705.216.86.192.34.1043397938.squirrel@www.la-rubber.com>

* 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