| From: | Mariya Rampurawala <Mariya(dot)Rampurawala(at)veritas(dot)com> |
|---|---|
| To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | PostgreSQL-12 replication. Check replication lag |
| Date: | 2020-08-04 15:23:22 |
| Message-ID: | AF8F0BC2-E663-4F1E-8ACA-6ABAE3E13B6B@veritas.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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, how can we check if the slave is up-to-date.
One way I found from the blogs is to compare the values of pg_last_wal_receive_lsn() and pg_last_wal_replay_lsn()
If these values are same, can we say that the slave is up-to-date?
Both these values I will fetch from the slave node. How will the slave ensure it is up-to-date, if the network between master and slave is broken?
Regards,
Mariya
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Raj Gandhi | 2020-08-04 20:35:16 | Postgres 12 - default value for text column |
| Previous Message | Alvaro Herrera | 2020-08-04 13:53:36 | Re: 12.3 replicas falling over during WAL redo |