| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Jeffrey(dot)Marshall(at)usitc(dot)gov, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [GENERAL] Permission Denied Error on pg_xlog/RECOVERYXLOG file |
| Date: | 2016-05-28 00:54:43 |
| Message-ID: | 31722.1464396883@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2016-05-26 12:44:51 -0400, Tom Lane wrote:
> 2016-04-27 17:02:06 EDT 572128cd.1811 [7-1] user=,db=,remote= FATAL: 42501:
> could not open file "pg_xlog/RECOVERYXLOG": Permission denied
> So, what's the permission of RECOVERYXLOG at that point? It's pretty
> weird that directly after running reason_command it's not readable.
s/not readable/not writable/. I doubt that it's a good idea for that
code to think that it can fail hard on non-writable files.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2016-05-28 00:57:59 | Re: [GENERAL] Permission Denied Error on pg_xlog/RECOVERYXLOG file |
| Previous Message | Andres Freund | 2016-05-28 00:44:54 | Re: [GENERAL] Permission Denied Error on pg_xlog/RECOVERYXLOG file |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2016-05-28 00:57:59 | Re: [GENERAL] Permission Denied Error on pg_xlog/RECOVERYXLOG file |
| Previous Message | Andres Freund | 2016-05-28 00:44:54 | Re: [GENERAL] Permission Denied Error on pg_xlog/RECOVERYXLOG file |