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 Magnus Hagander
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 CABUevExW2pb=6KqyttV3=vdVRA9UYj3oEZgDL6afJFh54b24rg@mail.gmail.com
Whole thread Raw
In response to 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>)
Responses Re: pg_basebackup: could not get transaction log end position from server: FATAL: could not open file "./pg_hba.conf~": Permission denied
Re: pg_basebackup: could not get transaction log end position from server: FATAL: could not open file "./pg_hba.conf~": Permission denied
List pgsql-hackers

On Fri, May 16, 2014 at 5:46 PM, Joshua D. Drake <jd@commandprompt.com> wrote:
At a minimum:

Check to see if there is going to be a permission error BEFORE the base backup begins:

starting basebackup:
  checking perms: ERROR no access to pg_hba.conf~ base backup will fail

That's pretty much what it does if you enable progress meter. I realize you don't necessarily want that one, but we could have a switch that still tells the server to measure the size, but not actually print the output? While it costs a bit of overhead to do that, that's certainly something that's a lot more safe than ignoring errors.
 
--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: pg_basebackup: could not get transaction log end position from server: FATAL: could not open file "./pg_hba.conf~": Permission denied
Next
From: Andres Freund
Date:
Subject: Re: pg_basebackup: could not get transaction log end position from server: FATAL: could not open file "./pg_hba.conf~": Permission denied