On Wed, Aug 05, 2020 at 06:36:15PM +, Mariya Rampurawala wrote:
> What I want to understand is that, in case of replication link
> failure, there will still be inserts happening at the master
> node. In that case, how will the slave know if it is up-to-date?
It cannot do that by itse
is that, in case of replication link failure, there
will still be inserts happening at the master node. In that case, how will the
slave know if it is up-to-date?
Regards,
Mariya
From: "Ahmed, Nawaz (Fuji Xerox Australia)"
Date: Wednesday, 5 August 2020 at 11:41 PM
To: Mariya Rampurawala ,
&
2020 1:23 AM
To: pgsql-gene...@postgresql.org
Subject: PostgreSQL-12 replication. Check replication lag
Hi,
I am working on providing HA for replication, using automation scripts.
My set up consists of two nodes, Master and Slave. When master fails, The slave
is promoted to master.
In case of sync
Hi,
I am working on providing HA for replication, using automation scripts.
My set up consists of two nodes, Master and Slave. When master fails, The slave
is promoted to master.
In case of sync replication, we do not check if the data is up-to-date on slave.
But in case of async replication
of the same db that was replicated from s1
- s3: subscription of the db from s2
When I did this, replication s1=>s2 stopped, and replication s2=>s3
never worked.
Is this not possible?
You'll have to share more details - error messages from the server log,
how you check that the replication stoppe
