Thanks for the suggestion.
I understand that wal_sender_timeout should be increased. Experience has
shown that for status-interval=1s it is necessary to configure wal_sender_timeout
to 15 seconds.
Nevertheless I found out that if I call
pg_basebackup -h host01 -U dbuser -D
/var/PostgresDb --wal-method=fetch -w
(using fetch method instead of default
stream method),
pg_basebackup completes successfully.
Best regards,
Andrei
From:
Stephen Frost <sfrost@xxxxxxxxxxx>
To:
AYahorau@xxxxxxxxxxx,
Cc:
MikalaiKeida@xxxxxxxxxxx,
pgsql-admin <pgsql-admin@xxxxxxxxxxxxxx>, Shreeyansh Dba <shreeyansh2014@xxxxxxxxx>
Date:
04/12/2018 18:38
Subject:
Re: pg_basebackup
fails: could not receive data from WAL stream: server closed the connection
unexpectedly
Greetings,
* AYahorau@xxxxxxxxxxx (AYahorau@xxxxxxxxxxx) wrote:
> Is there any relation/dependency between status-interval and
> wal_sender_timeot.?
Yes, if pg_basebackup doesn't ping the server with a status interval
within wal_sender_timeout amount of time then the server is going to
think it's disappeared.
> I am asking this because even if I set status-interval
for pg_basebackup
> to 1 second( the most frequent feedback) I get the same error:
Sure- if they're both set to 1s, you're likely to still see the issue.
Networks take time and systems can end up being busy, so having such a
very tight timeout is, frankly, unlikely to work out all that well for
you regardless.
You could try setting wal_sender_timeout to 2s or maybe 5s and see if
that works better.
Thanks!
Stephen
[attachment "signature.asc" deleted by Andrei Yahorau/IBA]
