From: Guy Fraser <guy@incentre.net>
To: pgsql-sql@postgresql.org
Subject: Re: Scheduling Events?
Date: Fri, 24 Jan 2003 11:46:02 -0700
Message-ID: <3E3189EA.7010105@incentre.net> (raw)
References: <Pine.LNX.4.44.0301241150460.12585-100000@matrix.gatewaynet.com>
<13296.1043422336@sss.pgh.pa.us>
Hi
I would agree that cron is probably the best solution.
You could have cron perform a query that has a trigger and performs all the
tasks you need done. As well you could create a trigger on other queries that
would perform the other things as well, but make sure it isn't a heavily used
query but instead a query that is run hourly or daily. As a backup for cron
you could manualy or using "anacron" or somthing similar run the query cron
should run on a regular basis, but you should make sure your trigger keeps an
entry in your database letting the other queries know when the update is
started and when it has finished. Using this check ensures you don't get
"overlapping" updates, and can also give you a clue to how much time the
updates are taking and possibly alert you to a "hung" update.
Guy
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: guy@incentre.net
Subject: Re: Scheduling Events?
In-Reply-To: <3E3189EA.7010105@incentre.net>
* 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