Subject: Re: Sync Rep for 2011CF1
From: "Joshua D. Drake" <jd@commandprompt.com>
Reply-To: jd@commandprompt.com
To: Robert Haas <robertmhaas@gmail.com>
Cc: pgsql-hackers@postgresql.org
In-Reply-To: <AANLkTikUxTM+6EaZ8S_OteDzCXaccsPVsd1U_ZUzM5i0@mail.gmail.com>
References: <1295127631.3282.100.camel@ebony>
	<AANLkTikbV8afeeC6-iESC4myeR5BUzg-YnTqCvKJ3qcO@mail.gmail.com>
	<AANLkTikUxTM+6EaZ8S_OteDzCXaccsPVsd1U_ZUzM5i0@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Organization: Command Prompt, Inc.
Date: Tue, 08 Feb 2011 12:26:17 -0800
Message-ID: <1297196777.18411.234.camel@jd-desktop>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Tue, 2011-02-08 at 13:53 -0500, Robert Haas wrote:

> That having been said, there is at least one part of this patch which
> looks to be in pretty good shape and seems independently useful
> regardless of what happens to the rest of it, and that is the code
> that sends replies from the standby back to the primary.  This allows
> pg_stat_replication to display the write/flush/apply log positions on
> the standby next to the sent position on the primary, which as far as
> I am concerned is pure gold.  Simon had this set up to happen only
> when synchronous replication or XID feedback in use, but I think
> people are going to want it even with plain old asynchronous
> replication, because it provides a FAR easier way to monitor standby
> lag than anything we have today.  I've extracted this portion of the
> patch, cleaned it up a bit, written docs, and attached it here.

Score! +1

JD

-- 
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579
Consulting, Training, Support, Custom Development, Engineering
http://twitter.com/cmdpromptinc | http://identi.ca/commandprompt