Received: from maia.hub.org (maia-2.hub.org [200.46.204.251])
	by mail.postgresql.org (Postfix) with ESMTP id CBA67B5DBE5
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Thu, 18 Aug 2011 18:42:00 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia,
	port 10024) with ESMTP id 53161-02 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Thu, 18 Aug 2011 21:41:54 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from nm1-vm4.bullet.mail.ne1.yahoo.com
	(nm1-vm4.bullet.mail.ne1.yahoo.com [98.138.91.161])
	by mail.postgresql.org (Postfix) with SMTP id 31980B5D803
	for <pgsql-admin@postgresql.org>; Thu, 18 Aug 2011 18:41:53 -0300 (ADT)
Received: from [98.138.90.55] by nm1.bullet.mail.ne1.yahoo.com with NNFMP;
	18 Aug 2011 21:41:53 -0000
Received: from [98.138.89.249] by tm8.bullet.mail.ne1.yahoo.com with NNFMP;
	18 Aug 2011 21:41:53 -0000
Received: from [127.0.0.1] by omp1041.mail.ne1.yahoo.com with NNFMP;
	18 Aug 2011 21:41:53 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 52459.44080.bm@omp1041.mail.ne1.yahoo.com
Received: (qmail 82459 invoked by uid 60001); 18 Aug 2011 21:41:53 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024;
	t=1313703712; bh=TpklpRBIRWJb/a2D3nKveZ/9ZhuqUyx4jIDD5cB8BFw=;
	h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type;
	b=yzcCZGvoqKOhFyi60idDeqAWwFp0mU4fMQZwfuYqjjTwNOKe7tjnBtBXz451z7/gUZCaOqQSaqbl7mb+3i7Mjd8pdWzwYgYJtJ8gBkaf8314Ybt8VagY9TcITCWTzAwd+602rnhKIFoWM6M5q1slVrUyp07xiGTPlIqMXHY04ZI=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type;
	b=1QN/0iKijIzOaCEB5UKmgqtRHIFLtg60xadP4/v9R56JhBxQ3WcNVuEdAzcKLYLZpUBtV7k20nBzfQtQCZc4CnfZdeSF5e/XK52h1QR/0cibeZLFeQT2WCa27GSVgZdmyqiMR3DNx2R3plpZDqHTrJilvSqSohxhR8UvQTmXxD4=;
X-YMail-OSG: NcnaRGQVM1lpjpHVaBfyNtLYSLt39a4jexFg0ZhcAfH8_OM
	7Rsbt9gY56.KcGTVDhKlp7IpbJk90EqcJiiZhiCoqYlwHvGho8V701b2xaqJ
	3yXIOA7vwZz8svwDGB7xaxxF0dZtaYdFhkZAJG69FjViyDiUZBkchB.MgjcZ
	mV0TuAprumZZRTpBaOwenXTN6Kp2H1Pk1S5F5BrG6E7hCZcMBwvj2vcpDch8
	Q8Z40W4bVz3vsZc0UZKjTN0z4v0yJan30kFAYnM2yPIrVp4612DDdmNLYKQC
	hNEve3_5J_cjl3knInahn0GGrHdGjBbDnzDM3YuLE4_dg5aqW2MixrhJHmIv
	RQ97XAFJi0Q0YgqkfOWcw8rGFM2vFr4lZ7KtWNk2hc05BFEWuzOTg
Received: from [64.61.91.74] by web120004.mail.ne1.yahoo.com via HTTP;
	Thu, 18 Aug 2011 14:41:52 PDT
X-Mailer: YahooMailWebService/0.8.113.313619
Message-ID: <1313703712.75602.YahooMailNeo@web120004.mail.ne1.yahoo.com>
Date: Thu, 18 Aug 2011 14:41:52 -0700 (PDT)
From: A J <s5aly@yahoo.com>
Reply-To: A J <s5aly@yahoo.com>
Subject: Validate standby against master
To: PG Admin <pgsql-admin@postgresql.org>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="1265908415-2136940051-1313703712=:75602"
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-0.365 tagged_above=-10 required=5 tests=BAYES_50=0.8,
	FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001,
	RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.167
X-Spam-Level: 
X-Archive-Number: 201108/173
X-Sequence-Number: 38160

--1265908415-2136940051-1313703712=:75602
Content-Type: text/plain; charset=us-ascii

What are the various ways in which I can validate that a standby (new or existing) is caught-up with the master ? For streaming replication setup in v9.x

--1265908415-2136940051-1313703712=:75602
Content-Type: text/html; charset=us-ascii

<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div>What are the various ways in which I can validate that a standby (new or existing) is caught-up with the master ? For streaming replication setup in v9.x</div><div><br></div></div></body></html>
--1265908415-2136940051-1313703712=:75602--