| From: | Mariel Cherkassky <mariel(dot)cherkassky(at)gmail(dot)com> |
|---|---|
| To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | question regarding BUG #14999 |
| Date: | 2019-06-08 15:21:14 |
| Message-ID: | CA+t6e1=hG4CEQ4UhxFr6EJfWLxNp8mvg1rc-0HOsV4D+7+_cZA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Hey,
I have pg 9.6 and as it seems I suffered from the same bug documented in
https://www.postgresql.org/message-id/20180104200633.17004.16377%40wrigleys.postgresql.org
From what I saw the root cause is that there is a file (most probably
server.key) that has only read only permissions (400). In my case, the
server.key permissions are set to 600 and not to 400. In addition, there
isnt any file with such permissions (400) in the data dir. I wanted to ask
why only read only permissions can cause this bug and if maybe it isnt
necessary the root cause.
Thanks.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mahmoud Moharam | 2019-06-10 06:24:26 | Postgres Replication stopped |
| Previous Message | Laurenz Albe | 2019-06-06 14:34:27 | Re: ERROR:::::: could not rename temporary statistics file ... |