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

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Andres Freund <andres(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_basebackup: could not get transaction log end position from server: FATAL: could not open file "./pg_hba.conf~": Permission denied
Date: 2014-05-16 17:01:48
Message-ID: 5376447C.6070903@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 05/16/2014 09:20 AM, Magnus Hagander wrote:
>
> On Fri, May 16, 2014 at 5:46 PM, Joshua D. Drake <jd(at)commandprompt(dot)com
> <mailto:jd(at)commandprompt(dot)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.

That seems reasonable.

JD

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2014-05-16 17:11:08 Re: chr() is still too loose about UTF8 code points
Previous Message Heikki Linnakangas 2014-05-16 16:43:55 Re: chr() is still too loose about UTF8 code points