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

From Heikki Linnakangas
Subject Re: Synchronous Log Shipping Replication
Date
Msg-id 48C6857E.4000402@enterprisedb.com
Whole thread Raw
In response to Re: Synchronous Log Shipping Replication  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Synchronous Log Shipping Replication  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Tom Lane wrote:
> Simon Riggs <simon@2ndQuadrant.com> writes:
>> On Tue, 2008-09-09 at 08:24 -0400, Tom Lane wrote:
>>> "Agreed"?  That last restriction is a deal-breaker.
> 
>> OK, I should have said *if wal_buffers are full* XLogInsert() cannot
>> advance to a new page while we are waiting to send or write. So I don't
>> think its a deal breaker.
> 
> Oh, OK, that's obvious --- there's no place to put more data.

Each WAL sender can keep at most one page locked at a time, right? So, 
that should never happen if wal_buffers > 1 + n_wal_senders.

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Synchronous Log Shipping Replication
Next
From: Tatsuo Ishii
Date:
Subject: Re: Common Table Expressions (WITH RECURSIVE) patch