From: | Chris Browne <cbbrowne(at)acm(dot)org> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: How to write jobs in postgresql |
Date: | 2005-09-07 03:53:53 |
Message-ID: | 603bohsfce.fsf@dba2.int.libertyrms.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
neuhauser(at)sigpipe(dot)cz (Roman Neuhauser) writes:
> # jnasby(at)pervasive(dot)com / 2005-08-15 20:25:20 -0500:
>> On Tue, Aug 09, 2005 at 03:26:27PM -0500, Guy Rouillier wrote:
>> > chiranjeevi.i wrote:
>> > > Hi Team Members,
>> > >
>> > > Is it possible to write jobs in postgresql & if possible how
>> > > should I write .please help me.
>> >
>> > See pgjob in pgfoundry: http://pgfoundry.org/projects/pgjob/. It's in
>> > the planning stages.
>>
>> Actually, it's currently in the going nowhere stage since no one's
>> expressed any interest in it. Anyone who's interested is encouraged to
>> join the mailing list and post what they'd like to see from the project.
>
> What's the advantage over system-native (cron etc) means?
You could doubtless do things with "pgcron" you cannot readily do with
cron, such as:
1. Expressing dependancies between jobs (e.g. - run A after running
B, don't start C if B is still running)
2. More specific time increments than cron offers (e.g. - heading
nearer to granularity of seconds)
3. An integrated way of logging what ran when (rather than either
stuffing logging code into each cron job or rummaging thru
cron logs)
4. You could use SQL queries to request information about jobs.
--
select 'cbbrowne' || '@' || 'cbbrowne.com';
http://www.ntlug.org/~cbbrowne/sap.html
"LISP car-and-cdr worlds are a more reasonable representation of the
things that make life interesting than fixed decimal(15) or FILE
OLDMSTR RECORD IS PAYROLL." -- Bernie Greenberg.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-09-07 04:19:19 | Re: Shared disk storage |
Previous Message | Bruno Wolff III | 2005-09-07 03:24:04 | Re: Shared disk storage |