Re: pg_basebackup fails: could not receive data from WAL stream: serverclosed the connection unexpectedly - Mailing list pgsql-admin

From AYahorau@ibagroup.eu
Subject Re: pg_basebackup fails: could not receive data from WAL stream: serverclosed the connection unexpectedly
Date
Msg-id OFD37D6500.8D41B158-ON43258359.00548653-43258359.00551D40@iba.by
Whole thread Raw
In response to Re: pg_basebackup fails: could not receive data from WAL stream:server closed the connection unexpectedly  (Stephen Frost <sfrost@snowman.net>)
Responses Re: pg_basebackup fails: could not receive data from WAL stream:server closed the connection unexpectedly  (Stephen Frost <sfrost@snowman.net>)
List pgsql-admin
Thanks Stephen,

Is there any relation/dependency between status-interval  and wal_sender_timeot.?


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:
pg_basebackup: could not receive data from WAL stream: server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.
pg_basebackup: child process exited with error 1

because the server terminates wal_sender due to replication timeout.

Best regards,
Andrei



From:        Stephen Frost <sfrost@snowman.net>
To:        AYahorau@ibagroup.eu,
Cc:        Shreeyansh Dba <shreeyansh2014@gmail.com>, MikalaiKeida@ibagroup.eu, pgsql-admin <pgsql-admin@postgresql.org>
Date:        04/12/2018 17:05
Subject:        Re: pg_basebackup fails: could not receive data from WAL stream: server closed the connection unexpectedly




Greetings,

* AYahorau@ibagroup.eu (AYahorau@ibagroup.eu) wrote:
> I reckon we can return to more conventional approach of postgres db
> synchronization:
> 1) SELECT pg_start_backup('label', true);
> 2) rsync/cp  $PGDATA directory;
> 3) SELECT pg_stop_backup();

It doesn't seem clear what the goal here is- if you are looking to have
two DB servers that are synchronized, then using pg_basebackup to get
the initial copy and then running PostgreSQL as a replica would be the
right approach.

I certainly wouldn't recommend trying to hack together something with
rsync or cp or using the exclusive backup mode at all- if the system
crashes when that exclusive backup is happening, the database won't come
back up.

> I have a question. What is your opinion about pg_basebackup utility and
> its behaviour for this condition?  Is it a bug? Should it be fixed?

No, I don't see any bug here, but if you adjust the timeout values on
the server then you need to tell pg_basebackup to send messages to the
server more frequently or it's going to get timed out.  That's what the
--status-interval option in pg_basebackup is for.

Thanks!

Stephen
[attachment "signature.asc" deleted by Andrei Yahorau/IBA]

pgsql-admin by date:

Previous
From: Stephen Frost
Date:
Subject: Re: pg_basebackup fails: could not receive data from WAL stream:server closed the connection unexpectedly
Next
From: Stephen Frost
Date:
Subject: Re: pg_basebackup fails: could not receive data from WAL stream:server closed the connection unexpectedly