Re: Streaming replication and non-blocking I/O - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Streaming replication and non-blocking I/O
Date
Msg-id 3f0b79eb0912082355kc122d5ai6af78354f380047b@mail.gmail.com
Whole thread Raw
In response to Re: Streaming replication and non-blocking I/O  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: Streaming replication and non-blocking I/O  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Dec 9, 2009 at 3:58 PM, Heikki Linnakangas
<heikki.linnakangas@enterprisedb.com> wrote:
> True. Another idea I had was to introduce a callback that backend libpq
> can call when the buffer fills. Walsender would set the callback to
> ProcessStreamMsgs().
>
> But if everyone is happy with just relying on the OS buffer to not fill
> up, let's just drop it.

The OS buffer is expected to be able to store a large number of
XLogRecPtr messages, because its size is small. So it's also OK
to just drop it.

Regards,

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


pgsql-hackers by date:

Previous
From: Jaime Casanova
Date:
Subject: Re: XLogInsert
Next
From: "Massa, Harald Armin"
Date:
Subject: Re: [PATCH] Windows x64 [repost]