Re: Sync Rep: First Thoughts on Code

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: Aidan Van Dyk <aidan(at)highrise(dot)ca>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Sync Rep: First Thoughts on Code
Date: 2008-12-11 15:17:50
Message-ID: 1229008670.13078.16.camel@hp_dx2400_1
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On Thu, 2008-12-11 at 17:07 +0200, Heikki Linnakangas wrote:
> Simon Riggs wrote:
> > On Thu, 2008-12-11 at 09:27 -0500, Aidan Van Dyk wrote:
> >
> >> But "catchup" *has* to be *done* before PostgreSQL can enter "sync rep".
> >
> > Not true. Please reread the thread where Heikki questions that and I
> > reply. This was Fujii-san's idea, which I now agree with.
>
> I think the confusion here is about what exactly "sync rep" means in
> this situation. It's true that you can start streaming the WAL before
> the standby has fully caught up.

Yep.

> But from the client's point of view,
> there's not much point in streaming the log *synchronously* and making
> the client to wait for the acknowledment from the standby, if the
> acknowledgment from the standby that WAL has be streamed up to point X,
> doesn't actually guarantee that the slave can recover all the way to
> that point.

I disagree. This morning I showed it was possible, given the
synchronisation I outlined.

There is a slight relaxation of that in the current proposal, so you
need to take that up if you see any problem there.

--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message KaiGai Kohei 2008-12-11 15:18:36 Re: Updates of SE-PostgreSQL 8.4devel patches (r1268)
Previous Message Aidan Van Dyk 2008-12-11 15:15:09 Re: Sync Rep: First Thoughts on Code