Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from
	<pgsql-admin-owner+M40633=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
	id 1TvsCb-0001ci-Bp
	for pgsql-admin@arkaria.postgresql.org; Thu, 17 Jan 2013 16:20:29 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
	by malur.postgresql.org with smtp (Exim 4.72) (envelope-from
	<pgsql-admin-owner+M40633=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
	id 1TvsCa-0004sS-So
	for pgsql-admin@arkaria.postgresql.org; Thu, 17 Jan 2013 16:20:28 +0000
Received: from makus.postgresql.org ([98.129.198.125])
	by malur.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <scott@journyx.com>) id 1TvsCa-0004sL-3f
	for pgsql-admin@postgresql.org; Thu, 17 Jan 2013 16:20:28 +0000
Received: from mail.journyx.com ([209.163.206.41] helo=mail.int.journyx.com)
	by makus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <scott@journyx.com>) id 1TvsCV-00031e-3u
	for pgsql-admin@postgresql.org; Thu, 17 Jan 2013 16:20:24 +0000
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mail.int.journyx.com (Postfix) with ESMTP id 81C32C46D7
	for <pgsql-admin@postgresql.org>; Thu, 17 Jan 2013 10:20:22 -0600 (CST)
X-Virus-Scanned: amavisd-new at zimbra.int.journyx.com
Received: from mail.int.journyx.com ([127.0.0.1])
	by localhost (mail.int.journyx.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id J9pyP2W9Qk-E for <pgsql-admin@postgresql.org>;
	Thu, 17 Jan 2013 10:20:17 -0600 (CST)
Received: from mail.int.journyx.com (zimbra.int.journyx.com [192.168.100.5])
	by mail.int.journyx.com (Postfix) with ESMTP id 3DAEAC46D9
	for <pgsql-admin@postgresql.org>; Thu, 17 Jan 2013 10:20:17 -0600 (CST)
Date: Thu, 17 Jan 2013 10:20:17 -0600 (CST)
From: Scott Whitney <scott@journyx.com>
Reply-To: Scott Whitney <swhitney@journyx.com>
To: pgsql-admin@postgresql.org
Message-ID: <18871234.487716.1358439617072.JavaMail.root@mail.int.journyx.com>
In-Reply-To: 
 <25940786.487525.1358439150642.JavaMail.root@mail.int.journyx.com>
Subject: Replication monitoring questions
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_487715_11424842.1358439617070"
X-Originating-IP: [192.168.100.188]
X-Mailer: Zimbra 7.2.0_GA_2669 (ZimbraWebClient - FF3.0 (Win)/7.2.0_GA_2669)
X-Pg-Spam-Score: -0.0 (/)
List-Archive: <http://archives.postgresql.org/pgsql-admin>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-admin.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@postgresql.org>
List-Post: <mailto:pgsql-admin@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-admin>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
X-Mailing-List: pgsql-admin
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

------=_Part_487715_11424842.1358439617070
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

I've got replication setup (streaming replication) between two 9.2.2 clusters. Everything went just fine on that, and it's working as expected. 

Now, obviously, I'll know if my primary goes down. I just monitor him as usual. 

How do I tell whether the standby has gone out of sync for whatever reason? 

Obviously, I can monitor this: 

ps -elf | grep "wal receiver" 

but is there a situation in which the wal receiver is running, but the replication is not working, or there are errors? I know about the replay/receive xlog locations, but those can be off due to lag, of course. 

What I want to know is whether there's a situation in which my standby is running, the receiver process is running, but "something" is wrong. 

Sorry this isn't more definite. I'm not quite sure what I'm looking for. 

Thanks, 
Scott 

------=_Part_487715_11424842.1358439617070
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><style type=3D'text/css'>p { margin: 0; }</style></head><body><=
div style=3D'font-family: times new roman,new york,times,serif; font-size: =
12pt; color: #000000'>I've got replication setup (streaming replication) be=
tween two 9.2.2 clusters. Everything went just fine on that, and it's worki=
ng as expected.<br><br>Now, obviously, I'll know if my primary goes down. I=
 just monitor him as usual.<br><br>How do I tell whether the standby has go=
ne out of sync for whatever reason?<br><br>Obviously, I can monitor this:<b=
r><br>ps -elf | grep "wal receiver"<br><br>but is there a situation in whic=
h the wal receiver is running, but the replication is not working, or there=
 are errors? I know about the replay/receive xlog locations, but those can =
be off due to lag, of course.<br><br>What I want to know is whether there's=
 a situation in which my standby is running, the receiver process is runnin=
g, but "something" is wrong.<br><br>Sorry this isn't more definite. I'm not=
 quite sure what I'm looking for.<br><br>Thanks,<br>Scott<br></div></body><=
/html>
------=_Part_487715_11424842.1358439617070--