Re: Fwd: Monitoring Replication on Master/Slave Postgres(9.1) - Mailing list pgsql-admin

From Gabriel Muñoz
Subject Re: Fwd: Monitoring Replication on Master/Slave Postgres(9.1)
Date
Msg-id CAP8pxBbE1YVLbcmMBCjoDysM_G_Ga4VWoKHOLg0XK-g4ha3rgQ@mail.gmail.com
Whole thread Raw
In response to Re: Fwd: Monitoring Replication on Master/Slave Postgres(9.1)  (Steve Crawford <scrawford@pinpointresearch.com>)
List pgsql-admin
I use "select * from pg_stat_replication;" and compare columns: sent_location | write_location | flush_location | replay_location

Gabriel.


On Wed, Nov 28, 2012 at 7:09 PM, Steve Crawford <scrawford@pinpointresearch.com> wrote:
On 11/28/2012 11:24 AM, Shams Khan wrote:
Thanks for the response Steve...It was really helpful:

Below are some doubts I wanted to clarify..please read and suggest.
Can we also check if replication was broken earlier...somehow due to power failure of some other reasons in past...The reason I am asking is I am getting some discrepancies in data between master and slave...? I want to know the reason of it...

What sort of discrepancies? I am unaware of situations in a properly configured and functioning system where the standby could be anything other than lagging the master but I didn't dig through release notes to see if there were any related bugs.


Cheers,
Steve



--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin

pgsql-admin by date:

Previous
From: "Andrew W. Gibbs"
Date:
Subject: base backup requirements for PITR
Next
From: Gabriel Muñoz
Date:
Subject: Re: DBA user in Postgres