Then after the maintenance, recv or fsync makes transaction commit wait for XLOG to be received or fsync-ed by the stand by database.
Further read
https://wiki.postgresql.org/wiki/Streaming_Replication#Synchronization_capability
From: Prashanth Reddy [mailto:prash4783@xxxxxxxxx]
Sent: Tuesday, July 18, 2017 8:36 AM
To: Maddali, Srinivas <Srinivas.Maddali@xxxxxxxxxx>; Ashish Tiwari <tashish786@xxxxxxxxx>
Cc: pgsql-admin@xxxxxxxxxxxxxx; pgus-general@xxxxxxxxxxxxxx; pgsql-sql@xxxxxxxxxxxxxx; pgsql-in-general@xxxxxxxxxxxxxx; pgsql-novice@xxxxxxxxxxxxxx
Subject: Re: [EXTERNAL] Re: [pgus-general] Steps to place standby database in read write
Hi Srinivas,
Thanks for reaching out to me.
We are not in the process of setting up the hot-standby.
we are in the process of testing the DR databases, so we want to place the standby database out of sync from PROD by disabling the replication on DR site , place the DR database in read-write mode for testing purpose, once the application testing is done, we
would like to place the DR database back in sync with PROD.
NOTE: For Hot-standby we are using rsync method.
another question on postgres database logs: Is there any other location for the log files apart from "/var/log/postgresql" location?
|
