Postgres Pro
Downloads
Home   >   mailing lists

Re: pg_basebackup: could not get transaction log end position from server: FATAL: could not open file "./pg_hba.conf~": Permission denied - Mailing list pgsql-hackers

From Andres Freund
Subject Re: pg_basebackup: could not get transaction log end position from server: FATAL: could not open file "./pg_hba.conf~": Permission denied
Date
Msg-id 20140516143036.GE28158@awork2.anarazel.de
Whole thread Raw
In response to pg_basebackup: could not get transaction log end position from server: FATAL: could not open file "./pg_hba.conf~": Permission denied  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: pg_basebackup: could not get transaction log end position from server: FATAL: could not open file "./pg_hba.conf~": Permission denied  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-hackers
Tree view 
Hi,

On 2014-05-16 07:28:42 -0700, Joshua D. Drake wrote:
> Can we get that fixed please? It seems rather bad behavior for pg_basebackup
> to fatal out because of the permissions on a backup file of all things.
> Instead, we should do WARNING and say skipped.

Doesn't sound like a good idea to me. We'd need to have a catalog of
common unimportant fileendings and such. We surely *do* want to error
out when we fail to copy an important file.

Greetings,

Andres Freund

-- Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services

pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: pg_basebackup: could not get transaction log end position from server: FATAL: could not open file "./pg_hba.conf~": Permission denied
Next
From: Amit Kapila
Date:
Subject: Re: Scaling shared buffer eviction