Re: How to start slave after pg_basebackup. Why min_wal_size and wal_keep_segments are duplicated

From: "Andrus" <kobruleht2(at)hot(dot)ee>
To: "pgsql-general" <pgsql-general(at)postgresql(dot)org>, "Adrian Klaver" <adrian(dot)klaver(at)aklaver(dot)com>
Subject: Re: How to start slave after pg_basebackup. Why min_wal_size and wal_keep_segments are duplicated
Date: 2020-05-31 21:45:17
Message-ID: 21E8CC88FA0044708D91626126C82ADE@dell2
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi!

>> Will wal_keep_segments keep segments also if named replication slot is
>> lot used ?
>Well if you are using a replication slot there is no point in using
>wal_keep_segments. Slots where created in, part at least, so you did not
>have to guess at a wal_keep_segments number.

I dont use slot.

>To really answer this we will need to see the exact commands you are
>using and the sequence they are done in.

Replication server is created 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
chmod --recursive --verbose 0700 /var/lib/postgresql/12/main
chown -Rv postgres:postgres /var/lib/postgresql/12/main
/etc/init.d/postgresql start

Andrus.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Stefan Keller 2020-05-31 22:35:21 Re: Oracle vs. PostgreSQL - a comment
Previous Message Andrus 2020-05-31 21:43:02 Re: How to start slave after pg_basebackup. Why min_wal_size and wal_keep_segments are duplicated