Re: How to start slave after pg_basebackup. Why min_wal_size and wal_keep_segments are duplicated - Mailing list pgsql-general

From Andrus
Subject Re: How to start slave after pg_basebackup. Why min_wal_size and wal_keep_segments are duplicated
Date
Msg-id 74A42D0ECD334244813128ADE21A2DD4@dell2
Whole thread Raw
In response to Re: How to start slave after pg_basebackup. Why min_wal_size andwal_keep_segments are duplicated  (Adrian Klaver <adrian.klaver@aklaver.com>)
List pgsql-general
Hi!

>> I want to create  hot standby async server using
>> /etc/init.d/postgresql stop
>> mv /var/lib/postgresql/12/main /var/lib/postgresql/12/mainold
>> pg_basebackup --write-recovery-conf -D /var/lib/postgresql/12/main
>I don't see where the base backup is being taken from just where it is going.

It is taken from VPS server over 20 Mbit public internet connection.
Both servers are running Debian Linux.

>> I dont receive WALs.
>If you are doing binary replication then you are receiving WALs. It just a matter of whether you are streaming them or
shipping
 
>them over complete.

Using wal_keep_segments=360 also causes same wal file not found error after pg_basebackup.
master server has 6GB wal files.  wal log during pg_basebackup is much slower than 360.
Maybe pg_basebackup skips wal segments . Maybe using wal_compression=on causes the issue.

How to fix this ?
How to create base backup so that cluster is tranferred over internet faster? Maybe it can transferred in compressed
formover 
 
internet.

Andrus.



pgsql-general by date:

Previous
From: Stefan Knecht
Date:
Subject: Re: Oracle vs. PostgreSQL - a comment
Next
From: Tanja Savic
Date:
Subject: RE: pg_ctl can't start db server