On Tue, Aug 14, 2018 at 12:14:59PM -0400, Tom Lane wrote:
> That seems like a pretty expensive thing to do, if there are lots of
> files ... and you'd still end up failing, so it's not moving the ball
> very far.
Yeah, I would think that with many small relations it is going to have a
measurable p
On 08/14/2018 09:14 AM, Tom Lane wrote:
Mike Cardwell 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 di
Greetings,
* Ron (ronljohnso...@gmail.com) wrote:
> On 08/14/2018 11:14 AM, Tom Lane wrote:
> >Mike Cardwell writes:
> >>pg_basebackup: could not get write-ahead log end position from server:
> >>ERROR: could not open file "./postgresql.conf~": Permission denied
> >>Now, I know what this error m
On 08/14/2018 12:14 PM, Ron wrote:
> Why is checking a bunch of file permissions anywhere close to being as
> expensive as transferring 1.5TB over a WAN link?
Normally it shouldn't be but I recently had postgres create ~13M .snap
files and just opendir() took longer than anyone would care to wait
On 08/14/2018 11:14 AM, Tom Lane wrote:
Mike Cardwell writes:
pg_basebackup: could not get write-ahead log end position from server:
ERROR: could not open file "./postgresql.conf~": Permission denied
Now, I know what this error means. There was a root owned file at
"/var/lib/pgsql/10/data/p
Mike Cardwell writes:
> pg_basebackup: could not get write-ahead log end position from server:
> ERROR: could not open file "./postgresql.conf~": Permission denied
> Now, I know what this error means. There was a root owned file at
> "/var/lib/pgsql/10/data/postgresql.conf~" which contained an o
Hi,
I was just setting up streaming replication for the first time. I ran
pg_basebackup on the slave. It copied 1.5TB of data. Then it errored
out with:
```
1498215035/1498215035 kB (100%), 1/1 tablespace
pg_basebackup: could not get write-ahead log end position from server:
ERROR: could not ope