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

2014-05-16 Thread Joshua D. Drake
On 05/16/2014 09:20 AM, Magnus Hagander wrote: On Fri, May 16, 2014 at 5:46 PM, Joshua D. Drake mailto:j...@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 perm

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

2014-05-16 Thread Andres Freund
On 2014-05-16 18:29:25 +0200, Magnus Hagander wrote: > On Fri, May 16, 2014 at 6:25 PM, Andres Freund wrote: > > > On 2014-05-16 18:20:35 +0200, Magnus Hagander wrote: > > > On Fri, May 16, 2014 at 5:46 PM, Joshua D. Drake > >wrote: > > > > > > > At a minimum: > > > > > > > > Check to see if ther

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

2014-05-16 Thread Magnus Hagander
On Fri, May 16, 2014 at 6:25 PM, Andres Freund wrote: > On 2014-05-16 18:20:35 +0200, Magnus Hagander wrote: > > On Fri, May 16, 2014 at 5:46 PM, Joshua D. Drake >wrote: > > > > > At a minimum: > > > > > > Check to see if there is going to be a permission error BEFORE the base > > > backup begins

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

2014-05-16 Thread Andres Freund
On 2014-05-16 18:20:35 +0200, Magnus Hagander wrote: > On Fri, May 16, 2014 at 5:46 PM, Joshua D. Drake > 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 acces

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

2014-05-16 Thread Magnus Hagander
On Fri, May 16, 2014 at 5:46 PM, Joshua D. Drake 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

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

2014-05-16 Thread Joshua D. Drake
On 05/16/2014 08:48 AM, Andres Freund wrote: Hi, On 2014-05-16 08:45:12 -0700, Joshua D. Drake wrote: Software is supposed to make our lives easier, not harder. I should be able to evaluate the errors for the conditions they create. This is why rsync is and for the forseeable future will be ki

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

2014-05-16 Thread Andres Freund
Hi, On 2014-05-16 08:45:12 -0700, Joshua D. Drake wrote: > Software is supposed to make our lives easier, not harder. I should be able > to evaluate the errors for the conditions they create. This is why rsync is > and for the forseeable future will be king for creating base backups. It's dangero

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

2014-05-16 Thread Joshua D. Drake
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 JD -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your

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

2014-05-16 Thread Joshua D. Drake
On 05/16/2014 08:19 AM, Tom Lane wrote: pg_hba.conf~ is not an important file. Rather than blaming the messenger, you should be asking why there are files in $PGDATA that the server can't read. That's a recipe for trouble no matter what. Or in words of one syllable: this is a bug in your edi

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

2014-05-16 Thread Andres Freund
On 2014-05-16 08:13:04 -0700, Joshua D. Drake wrote: > On 05/16/2014 07:30 AM, Andres Freund wrote: > > > >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

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

2014-05-16 Thread Tom Lane
"Joshua D. Drake" writes: > On 05/16/2014 07:30 AM, Andres Freund wrote: >> 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,

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

2014-05-16 Thread Joshua D. Drake
On 05/16/2014 07:30 AM, Andres Freund wrote: 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 skipp

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

2014-05-16 Thread Andres Freund
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.

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

2014-05-16 Thread Joshua D. Drake
Hello, 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. JD -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes