Re: Synchronous Log Shipping Replication - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Synchronous Log Shipping Replication
Date
Msg-id 1220974998.3913.522.camel@ebony.2ndQuadrant
Whole thread Raw
In response to Re: Synchronous Log Shipping Replication  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
On Tue, 2008-09-09 at 18:26 +0300, Heikki Linnakangas wrote:
> Simon Riggs wrote:
> > Don't understand. I am referring to the logic at the top of
> > AdvanceXLInsertBuffer(). We would need to wait for all people reading
> > the contents of wal_buffers. 
> 
> Oh, I see.
> 
> If a slave falls behind, how does it catch up? 

That is the right question.

> I guess you're saying 
> that it can't fall behind, because the master will block before that 
> happens. Also in asynchronous replication? 

Yes, it can fall behind in async mode. sysadmin must not let it.

> And what about when the slave 
> is first set up, and needs to catch up with the master?

We need an initial joining mode while they "match speed". We must allow
for the case where the standby has been recycled, or the network has
been down for a medium-long period of time.

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



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Synchronous Log Shipping Replication
Next
From: "Pavel Stehule"
Date:
Subject: Re: Common Table Expressions (WITH RECURSIVE) patch