Re: Keepalive for max_standby_delay - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Keepalive for max_standby_delay
Date
Msg-id AANLkTimn-Q3QFejMk7px6x3PPvec2EowDNA6l-Nka9J6@mail.gmail.com
Whole thread Raw
In response to Re: Keepalive for max_standby_delay  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
On Wed, Jun 2, 2010 at 2:27 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
> Syncing two servers in replication is common practice, as has been
> explained here; I'm still surprised people think otherwise. Measuring
> the time between two servers is the very purpose of the patch, so the
> synchronisation is not a design flaw, it is its raison d'etre.

I think the purpose of the patch should not be to measure the time
difference between servers, but rather the replication delay.  While I
don't necessarily agree with Tom's statement that this is must-fix, I
do agree that it would be nicer if we could avoid depending on time
sync.  Yeah, I keep my servers time synced, too.  But, shit happens.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company


pgsql-hackers by date:

Previous
From: Chris Browne
Date:
Subject: Re: Exposing the Xact commit order to the user
Next
From: Tom Lane
Date:
Subject: "caught_up" status in walsender