On Thu, Jul 1, 2010 at 12:19 PM, Michael Tharp
<gxti(at)partiallystapled(dot)com> wrote:
> That said, as Martin mentions one can easily place the log directory outside
> of the data directory and set appropriate directory permissions.

If I can offer my $0.02, I recently solved such a problem on SuSE
Linux with apache logs. I used the ACL support on ext3 to give a
specific group read-only access:

cd /var/log
# Add an ACL for the 'www' user
setfacl -m u:www:r-x apache2
setfacl -m u:www:r-- apache2/*
# Modify the default ACL so that new files get 'r' for user
setfacl -d -m u:www:r-- apache2

Just pointing out that this problem is solvable on systems that
support ACLs w/o patching postgres.

In response to

• Re: log files and permissions at 2010-07-01 17:19:16 from Michael Tharp

pgsql-hackers by date

Next:	From: Robert Haas	Date: 2010-07-01 20:12:40
	Subject: pgsql: Allow copydir() to be interrupted.
Previous:	From: Michael Tharp	Date: 2010-07-01 17:19:16
	Subject: Re: log files and permissions