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:43:02
Message-ID: 246B62BD5BB44DCE8AEB15CA9723CDCE@dell2
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi!

>In addition to my most recent questions:
>What are you trying to achieve?

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

>In other words why do a pg_basebackup if you have a standby receiving WALs?

I dont receive WALs.

Andrus.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Andrus 2020-05-31 21:45:17 Re: How to start slave after pg_basebackup. Why min_wal_size and wal_keep_segments are duplicated
Previous Message Paul Förster 2020-05-31 21:35:33 Re: How to start slave after pg_basebackup. Why min_wal_size and wal_keep_segments are duplicated