From: | Rod Taylor <rbt(at)rbt(dot)ca> |
---|---|
To: | Þórhallur Hálfdánarson <tolli(at)tol(dot)li> |
Cc: | Andrew Sullivan <andrew(at)libertyrms(dot)info>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Scheduled jobs |
Date: | 2003-05-13 15:07:55 |
Message-ID: | 1052838474.33140.14.camel@jester |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 2003-05-13 at 10:48, Þórhallur Hálfdánarson wrote:
> -*- Andrew Sullivan <andrew(at)libertyrms(dot)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.
--
Rod Taylor <rbt(at)rbt(dot)ca>
PGP Key: http://www.rbt.ca/rbtpub.asc
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2003-05-13 15:43:11 | Re: GUC and postgresql.conf docs |
Previous Message | Kaare Rasmussen | 2003-05-13 15:04:52 | Re: Scheduled jobs |