Re: Synchronous replication patch v2

From: "Fujii Masao" <masao(dot)fujii(at)gmail(dot)com>
To: "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: "Simon Riggs" <simon(at)2ndquadrant(dot)com>, pavan(dot)deolasee(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Synchronous replication patch v2
Date: 2008-11-16 10:02:26
Message-ID: 3f0b79eb0811160202o6753ac55j597024992b380dd5@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Nov 15, 2008 at 2:00 AM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> Fujii Masao wrote:
>>
>> Attached is the latest version of Synch Rep patch.
>
> Why do we need a separate XLogsndRqst variable in shared memory? Don't we
> always want to send the WAL up to the same point as we flush it?

It's because the backends flush and send the WAL concurrently. I mean that
the backend might request for the WAL to be sent up to the further point while
another backend is writing it. If that variable is not separated, the backend
cannot request until the former flushing finishes.

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Oleg Serov 2008-11-16 10:03:59 Re: Pl/Perl function: Speed of the First time executing pl/perl function in connection;
Previous Message Oleg Serov 2008-11-16 09:59:49 Re: Pl/Perl function: Speed of the First time executing pl/perl function in connection;