From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | cestel(at)covermymeds(dot)com |
Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #13362: pg_basebackup not working in 9.4.2 |
Date: | 2015-05-27 17:43:39 |
Message-ID: | CAKFQuwbdQ7eKFBnSRfn+VKpbC1aM_0GKLkFpyRN5qU_3mUKiEg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Wed, May 27, 2015 at 10:38 AM, <cestel(at)covermymeds(dot)com> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 13362
> Logged by: CJ Estel
> Email address: cestel(at)covermymeds(dot)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 unable
> to start the postgres service with permission related issues. I first get
> 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 error
> 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.
>
>
You've hit a known bug:
https://wiki.postgresql.org/wiki/May_2015_Fsync_Permissions_Bug
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Porte, Alexander | 2015-05-27 21:39:48 | Upsert functions spinlock when doing insert first. |
Previous Message | cestel | 2015-05-27 17:38:43 | BUG #13362: pg_basebackup not working in 9.4.2 |