Re: pg_basebackup fails with Could not stat file or directory "./.pg_hba.conf.un~"
| От | David G. Johnston |
|---|---|
| Тема | Re: pg_basebackup fails with Could not stat file or directory "./.pg_hba.conf.un~" |
| Дата | |
| Msg-id | CAKFQuwY495XmkvwUH_-pNp=-HdwO3yhFjGZYD7nLYWWxbmqAQw@mail.gmail.com обсуждение исходный текст |
| Ответ на | pg_basebackup fails with Could not stat file or directory "./.pg_hba.conf.un~" ("Stephens, Gary" <Gary.Stephens@ehi.com>) |
| Ответы |
Re: pg_basebackup fails with Could not stat file or directory "./.pg_hba.conf.un~"
|
| Список | pgsql-bugs |
On Tue, Mar 7, 2023 at 1:37 PM Stephens, Gary <Gary.Stephens@ehi.com> wrote:
It's unclear to me why pg_basebackup is trying to read this file.
Because that is what it is documented to do:
> The backup will include all files in the data directory and tablespaces, including the configuration files and any additional files placed in the directory by third parties, except certain temporary files managed by PostgreSQL.
It's also unclear why it's failing when it does try to read it, since the file has the same permissions and security context that should allow the instance to read it (even though the backup really shouldn’t need to read it).
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.
David J.
В списке pgsql-bugs по дате отправления: