Re: Lockfile restart failure is still there :-( - Mailing list pgsql-hackers

From Greg Stark
Subject Re: Lockfile restart failure is still there :-(
Date
Msg-id 87ll8liulb.fsf@stark.xeocode.com
Whole thread Raw
In response to Re: Lockfile restart failure is still there :-(  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane <tgl@sss.pgh.pa.us> writes:

> We need to be able to write in the whole directory, not just the
> lockfile.  But actually the point I am making above is in your favor:
> after adding a check on ownership, it would be a matter of your
> protection wishes what the directory protections need to be.  Right
> now that check is an integral part of some non-obvious safety
> considerations.

Ah, I see. So yes, I was annoyed at last once when I changed permissions on
the postgres data directory and got errors telling me not to do that.

-- 
greg



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: corrupted tuple (header?), pg_filedump output
Next
From: Christopher Kings-Lynne
Date:
Subject: Re: Changing the default wal_sync_method to open_sync for