| From: | Dick Snippe <Dick(dot)Snippe(at)tech(dot)omroep(dot)nl> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Dick Snippe <Dick(dot)Snippe(at)tech(dot)omroep(dot)nl>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #2088: logfiles only readable by instance owner |
| Date: | 2005-12-02 08:41:53 |
| Message-ID: | 20051202084153.GA16947@tech.omroep.nl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Dec 02, 2005 at 12:30:17AM -0500, Tom Lane wrote:
> "Dick Snippe" <Dick(dot)Snippe(at)tech(dot)omroep(dot)nl> writes:
> > setting umask 077 makes sense for the data files, but not per se for the
> > logfile.
>
> The logfile typically contains data just as sensitive as the data files,
true.
> so I disagree.
we run postgresql as a database engine behind a number of websites.
Typically all the data in the database is public data . It would be very
nice if there was a method of letting our developers _read_ the logfile,
without giving them _write_ access to the data files.
What wrong with making this configurable?
--
Dick Snippe - een Coordinator Publieke Omroep Internet Services
Gebouw 12.401 (peperbus) Sumatralaan 45 Hilversum \ fight war
tel +31 35 6774252, email beheer(at)omroep(dot)nl []() \ not wars
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Arjen van der Meijden | 2005-12-02 12:34:14 | Re: BUG #2075: Strange choice of bitmap-index-scan |
| Previous Message | Weiss, Wilfried | 2005-12-02 07:53:14 | Re: BUG #2083: initdb fails with: child process was terminated by signal 11 |