Re: Scheduled jobs - Mailing list pgsql-hackers

From scott.marlowe
Subject Re: Scheduled jobs
Date
Msg-id Pine.LNX.4.33.0305131059160.29026-100000@css120.ihs.com
Whole thread Raw
In response to Re: Scheduled jobs  (Rod Taylor <rbt@rbt.ca>)
List pgsql-hackers
On 13 May 2003, Rod Taylor wrote:

> On Tue, 2003-05-13 at 10:48, Þórhallur Hálfdánarson wrote:
> > -*- Andrew Sullivan <andrew@libertyrms.info> [ 2003-05-13 14:42 ]:
> > > On Tue, May 13, 2003 at 01:33:25PM +0000, ??rhallur H?lfd?narson wrote:
> > > > The suggestion on using ident was to eliminate the need for storing
> > > > passwords in the first place...
> > >
> > > But how are you going to let them run scheduled jobs inside the
> > > postmaster if they can't be authenticated, then?  You either have to
> > > use .pgpass, user kerberos, or use ident; nothing else is safe in the
> > > context you're discussing.  I don't understand the problem.
> >
> > I was simply pointing out some scenarios when scheduled jobs are nice. :-)
> >
> > I believe you have to be authenticated to *create* jobs... and would probably run as the owner, if it gets
implemented.
>
> Wouldn't it make more sense to modify cron to be able to read scheduling
> details out of the database -- rather than trying to modify PostgreSQL
> to try to feed cron?
>
> See examples of FTP, DNS, etc. software that can read authentication
> elements from databases -- and the lack of DBs that have knowledge of
> how to push data into those services.

Bingo, Rod.  You obviously reached across the miles into my head and stole
that from my brain, because honestly I was about 30 seconds from posting
the same thing.



pgsql-hackers by date:

Previous
From: "Zeugswetter Andreas SB SD"
Date:
Subject: Re: LIKE indexing proposal
Next
From: Tom Lane
Date:
Subject: Re: GUC and postgresql.conf docs