| From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
|---|---|
| To: | Brook Milligan <brook(at)trillium(dot)NMSU(dot)Edu> |
| Cc: | maillist(at)candle(dot)pha(dot)pa(dot)us, hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] postmaster crash and .s.pgsql file |
| Date: | 1998-01-29 20:10:15 |
| Message-ID: | Pine.NEB.3.95.980129150827.7021V-100000@hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 29 Jan 1998, Brook Milligan wrote:
> No, "normal" users shouldn't be allowed to do so, obviously. But, are
> there real systems in which a database maintainer (i.e., user
> postgres) cannot cooperate with the system admin (i.e., user root) to
> accomplish this? In practice, is it really envisioned that postgres
> should be _so_ distinct from the system? For example, don't most
> people run the postmaster from the system startup scripts, and isn't
> that the same thing? How did those commands get inserted into the
> startup scripts if not by root?
I do not feel that it is appropriate for a non-root program (which
PostgreSQL is) to require a systems administrator to make permissions
related changed to a directory for it to run, period.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Martin | 1998-01-29 20:19:38 | Re: [HACKERS] postmaster crash and .s.pgsql file |
| Previous Message | Brook Milligan | 1998-01-29 19:10:14 | Re: [HACKERS] postmaster crash and .s.pgsql file |