| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 15:53:22 |
| Message-ID: | 53763472.2030605@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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 king for creating base backups.
>
> It's dangerous to ignore errors rsync errors other than 'file
> vanished'. This hardly is an argument for your position.
Are you reading what I write?
I said. "I should be able to evaluate the errors for the conditions they
create."
I never suggested ignoring anything. The point is RSYNC gives me a
chance at success, pg_basebackup does not (in respect to this specific
condition).
JD
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2014-05-16 16:20:35 | Re: pg_basebackup: could not get transaction log end position from server: FATAL: could not open file "./pg_hba.conf~": Permission denied |
| Previous Message | Andres Freund | 2014-05-16 15:48:42 | Re: pg_basebackup: could not get transaction log end position from server: FATAL: could not open file "./pg_hba.conf~": Permission denied |