On Sat, Dec 18, 2004 at 03:01:54PM -0600, Jim C. Nasby wrote:
> Can you open-source your code? I'm sure others would benefit from it.
Eh. Big chunks of it are application specific, and a fair bit of the
rest uses some commercial libraries. I'll see what I can do.
(It'd be worth it to kill the monthly "why don't we do cron in the DB?"
thread :) )
Cheers,
Steve
> On Thu, Dec 16, 2004 at 09:37:04AM -0800, Steve Atkins wrote:
> > On Thu, Dec 16, 2004 at 10:12:46AM +0100, Marco Colombo wrote:
> > > On Wed, 15 Dec 2004, Jim C. Nasby wrote:
> > >
> > > >No, PostgreSQL doesn't have an equivalent to Oracle's dbms_job, but this
> > > >is a question that comes up pretty often. I think the bulk of the work
> > > >to make this happen could be done outside of the core database, so it
> > > >seems a good candidate for pgfoundry.
> > >
> > > What's wrong with at, cron, and some trivial shell scripting?
> > > (This is a real question, I wonder what advantages dbms_job has.)
> >
> > I don't know about dbms_job, but I implemented a simple cron-a-like in
> > postgresql for one of my apps so that database clients can schedule
> > events. The clients don't have access to a shell on the DB server,
> > it's a completely separate security domain. And the clients may not
> > even be powered up when an event is due to fire, so running cron there
> > isn't going to work either.