From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: fsync bug faq for publication? |
Date: | 2015-05-26 18:20:58 |
Message-ID: | 5564B98A.40600@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 05/26/2015 10:57 AM, Tom Lane wrote:
> Josh Berkus <josh(at)agliodbs(dot)com> writes:
>> Where did we get the idea that this issue only affects symlinked files?
>
> Nobody said any such thing. My point was that permissions and ownership
> both have to be looked at. The Debian situation is that there are symlinks
> in $PGDATA pointing at root-owned files, and those files are (we think)
> also used by other services; so Magnus' point was that you'd probably
> better copy those files not modify their ownership/permissions in situ.
Updated, please make further corrections so I can get an announcement
out ASAP. Thanks!
https://wiki.postgresql.org/wiki/May_2015_Fsync_Permissions_Bug
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2015-05-26 18:47:36 | Re: ERROR: MultiXactId xxxx has not been created yet -- apparent wraparound |
Previous Message | Tom Lane | 2015-05-26 17:57:28 | Re: fsync bug faq for publication? |