From: Stephen Frost <sfrost@snowman.net>
To: AYahorau@ibagroup.eu
Cc: MikalaiKeida@ibagroup.eu, pgsql-admin <pgsql-admin@postgresql.org>
Cc: Shreeyansh Dba <shreeyansh2014@gmail.com>
Subject: Re: pg_basebackup fails: could not receive data from WAL stream: server closed the connection unexpectedly
Date: Tue, 4 Dec 2018 10:38:14 -0500
Message-ID: <20181204153814.GP3415@tamriel.snowman.net> (raw)
In-Reply-To: <OFD37D6500.8D41B158-ON43258359.00548653-43258359.00551D40@iba.by>
References: <OF54569A25.1AF98674-ON43258358.002D80F2-43258358.00304DB9@iba.by>
<CAGDYbUPqEkPf9Y113AdaSUv33m27Z5xyjnykFDYzmTUqy+dk_A@mail.gmail.com>
<OF4CC3D4EF.4E5A434D-ON43258359.0044B5C1-43258359.004655F6@iba.by>
<20181204140512.GO3415@tamriel.snowman.net>
<OFD37D6500.8D41B158-ON43258359.00548653-43258359.00551D40@iba.by>
Greetings,
* AYahorau@ibagroup.eu (AYahorau@ibagroup.eu) 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
Attachments:
signature.asc (application/pgp-signature, 818B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: sfrost@snowman.net, AYahorau@ibagroup.eu, shreeyansh2014@gmail.com
Subject: Re: pg_basebackup fails: could not receive data from WAL stream: server closed the connection unexpectedly
In-Reply-To: <20181204153814.GP3415@tamriel.snowman.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox