Re: pg_rewind - Mailing list pgsql-admin

From Laurenz Albe
Subject Re: pg_rewind
Date
Msg-id 7389f3b042bed5d6b8fcf4cbf890fc932bc7963e.camel@cybertec.at
Whole thread Raw
In response to RE: pg_rewind  (<soumik.bhattacharjee@kpn.com>)
List pgsql-admin
On Mon, 2020-01-27 at 16:01 +0000, soumik.bhattacharjee@kpn.com wrote:
> I set the "wal_log_hints = on" , but enabling this parameter "on" in new MASTER(old SLAVE) needs a restart--
> which I cannot do as all application transactions are going on there now.
> 
> Also I used pg_rewind in old MASTER(which now I want to make as new SLAVE) and it was successful,
> but this also needs restart of new MASTER(old SLAVE) which is again an issue.
> 
> Command used: ./pg_rewind -D $PGDATA --source-server='host=<IP Address> port=5432 user=postgres password=xxxx
> 
> Could you please suggest how to get this to work to keep the MASTER(old SLAVE) up & running and make the old
MASTER(newSLAVE)
 

If you want to use "pg_rewind", you have to plan for that ahead of time
by either using data page checksums or enabling "wal_log_hints".

The first requires longer don time, the second a restart.
There is no way to do that retroactively.

Just use "pg_basebackup" to create a new standby, and enable
"wal_log_hints" next time you get a chance to restart.

Yours,
Laurenz Albe
-- 
Cybertec | https://www.cybertec-postgresql.com




pgsql-admin by date:

Previous
From:
Date:
Subject: RE: pg_rewind
Next
From: dbatoCloud Solution
Date:
Subject: Looking for postgresql database administration guidelines needed forpg clustering activities