Re: How to write jobs in postgresql

From: "Guy Rouillier" <guyr(at)masergy(dot)com>
To: "Roman Neuhauser" <neuhauser(at)sigpipe(dot)cz>, "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: How to write jobs in postgresql
Date: 2005-09-06 21:29:31
Message-ID: CC1CF380F4D70844B01D45982E671B239E8AA0@mtxexch01.add0.masergy.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Roman Neuhauser wrote:
> # 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?

Search the archives, you'll find numerous discussions on this topic,
including the one that prompted Jim to create the project. As of now,
the project is pre-concept stage, making it impossible to identify its
advantages. One possible advantage would be recording job schedules in
the database where they can be easily managed, but that's small. A
bigger advantage can be seen in the approach that Oracle takes, where
authentication happens when the job is created. So you don't need to
provide credentials at run time, which in the case of cron jobs would
mean putting passwords into shell scripts.

--
Guy Rouillier

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Kevin Barnard 2005-09-06 21:37:56 Help with row locks on 7.4 to 8.0 migration
Previous Message Ben 2005-09-06 21:17:59 Basic locking question