| From: | Francisco Olarte <folarte(at)peoplecall(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | "Stephens, Gary" <Gary(dot)Stephens(at)ehi(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_basebackup fails with Could not stat file or directory "./.pg_hba.conf.un~" |
| Date: | 2023-03-08 09:55:36 |
| Message-ID: | CA+bJJbzuJPqGgYwrLeVKJh6GgPUSB6XdD38yLmFcdEpNM-zq_A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi David:
On Tue, 7 Mar 2023 at 22:32, David G. Johnston
<david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> Understandable, but not a pg_basebackup bug that it is being told it lacks permission. But I suspect there is file locking involved and it isn't a file permission problem.
Besides locking I've encountered this kind of problems with people
having a habit of editing non-root-owned config files as root with
editors which do not take care of setting permissions. An ls -l of the
offending file is normally useful, or the version with all extended
acl/attrs which I'm unable to recall now.
Francisco Olarte.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2023-03-08 11:57:20 | Re: BUG #17368: Assert failed in GetSafeSnapshot() for SERIALIZABLE READ ONLY DEFERRABLE transaction |
| Previous Message | Alexander Lakhin | 2023-03-08 06:00:00 | Re: BUG #17811: Replacing an underlying view breaks OLD/NEW tuple when accessing it via upper-level view |