Re: BUG #13362: pg_basebackup not working in 9.4.2 - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: BUG #13362: pg_basebackup not working in 9.4.2
Date
Msg-id CAKFQuwbdQ7eKFBnSRfn+VKpbC1aM_0GKLkFpyRN5qU_3mUKiEg@mail.gmail.com
Whole thread Raw
In response to BUG #13362: pg_basebackup not working in 9.4.2  (cestel@covermymeds.com)
List pgsql-bugs
On Wed, May 27, 2015 at 10:38 AM, <cestel@covermymeds.com> wrote:

> The following bug has been logged on the website:
>
> Bug reference:      13362
> Logged by:          CJ Estel
> Email address:      cestel@covermymeds.com
> PostgreSQL version: 9.4.2
> Operating system:   RHEL7
> Description:
>
> #SUMMARY
> On postgres 9.4.2 I can successfully run pg_basebackup, but then am unabl=
e
> to start the postgres service with permission related issues.  I first ge=
t
> an error on a file that is there due to our log rotation process.  This
> file
> is owned by postgres and is readable.  If I remove that file (as it isn't
> needed by postgres in any way), it then gives me a similar permission err=
or
> on my server.crt SSL file.  This file is also owned by postgres and
> readable.  Performing the same steps on 9.4.1, I do not have any issues.
> Below is output from my SOURCE and DESTINATION servers.  In the examples
> provided, I am not setting up a recovery.conf file, but in my tests with
> that it does not improve the likelihood that I will be able to start the
> server.
>
>
=E2=80=8BYou've hit a known bug:

https://wiki.postgresql.org/wiki/May_2015_Fsync_Permissions_Bug

David J.
=E2=80=8B

pgsql-bugs by date:

Previous
From: cestel@covermymeds.com
Date:
Subject: BUG #13362: pg_basebackup not working in 9.4.2
Next
From: "Porte, Alexander"
Date:
Subject: Upsert functions spinlock when doing insert first.