Re: Replication lag from transaction logs

From: Fabio Pardi <f(dot)pardi(at)portavita(dot)eu>
To: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: Replication lag from transaction logs
Date: 2018-06-18 12:56:28
Message-ID: 975db215-0ba1-0a36-178d-dd4078fc0d50@portavita.eu
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-admin

That I know, if standby is down, you cannot know exactly the last applied transaction log file.

But you could get agross estimate if you check how many WAL files is the standby behind, just listing the WAL files on the master and on the standby.

Given that you can login on the standby machine.

regards,

fabio pardi

On 18/06/18 14:43, Debraj Manna wrote:
> Is it possible to figure out the replication lag from transaction log files in the slave and master without querying postgres on the slave? Basically figuring out the replication lag in a slave when the postgres is down in that slave.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Keith 2018-06-18 13:22:08 Re: Replication lag from transaction logs
Previous Message Debraj Manna 2018-06-18 12:43:36 Replication lag from transaction logs