From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Mike Cardwell <mike(dot)cardwell(at)hardenize(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: pg_basebackup failed to read a file |
Date: | 2018-08-14 18:37:27 |
Message-ID: | 0e4297d8-5399-8489-6f58-12c3607cbc79@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 08/14/2018 09:14 AM, Tom Lane wrote:
> Mike Cardwell <mike(dot)cardwell(at)hardenize(dot)com> writes:
>
> It'd be nice to have a more coherent theory about what needs to be copied
> or not, and not fail on files that could simply be ignored. Up to now
> we've resisted having any centrally defined knowledge of what can be
> inside a PG data directory, but maybe that bullet needs to be bitten.
This is not the first time, nor the second time this issue has arisen. I
would think we would know that a coherent theory or at least
semi-coherent theory would be pretty easy to resolve. Granted, we can't
reasonably know what is going on under base but under the / of PGDATA,
we know *exactly* what files should and should not be in there.
JD
--
Command Prompt, Inc. || http://the.postgres.company/ || @cmdpromptinc
*** A fault and talent of mine is to tell it exactly how it is. ***
PostgreSQL centered full stack support, consulting and development.
Advocate: @amplifypostgres || Learn: https://postgresconf.org
***** Unless otherwise stated, opinions are my own. *****
From | Date | Subject | |
---|---|---|---|
Next Message | Martín Marqués | 2018-08-14 19:15:12 | Re: upgrading from pg 9.3 to 10 |
Previous Message | Peter J. Holzer | 2018-08-14 18:28:09 | Re: Duplicating data folder without tablespace, for read access |