Re: The way to know whether the standby has caught up with the master - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: The way to know whether the standby has caught up with the master
Date
Msg-id BANLkTimopsxjt-OPr7Z62D7q7c_-E4Ao=g@mail.gmail.com
Whole thread Raw
In response to Re: The way to know whether the standby has caught up with the master  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: The way to know whether the standby has caught up with the master  (David Fetter <david@fetter.org>)
List pgsql-hackers
On Wed, May 25, 2011 at 6:16 AM, Heikki Linnakangas
<heikki.linnakangas@enterprisedb.com> wrote:

>> To achieve that, I'm thinking to change walsender so that, when the
>> standby
>> has caught up with the master, it sends back the message indicating that
>> to
>> the standby. And I'm thinking to add new function (or view like
>> pg_stat_replication)
>> available on the standby, which shows that info.
>
> By the time the standby has received that message, it might not be caught-up
> anymore because new WAL might've been generated in the master already.

AFAICS, this is an exact case of the Byzantine General's problem.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Proposal: Another attempt at vacuum improvements
Next
From: Heikki Linnakangas
Date:
Subject: Nested CASE-WHEN scoping