Re: Replication server timeout patch - Mailing list pgsql-hackers

From Daniel Farina
Subject Re: Replication server timeout patch
Date
Msg-id AANLkTinSQUoMoaBJ8ASFvZ4-iuUbp5tcbSwxpZfV1WwH@mail.gmail.com
Whole thread Raw
In response to Re: Replication server timeout patch  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: Replication server timeout patch  (Simon Riggs <simon@2ndQuadrant.com>)
Re: Replication server timeout patch  (Robert Haas <robertmhaas@gmail.com>)
Re: Replication server timeout patch  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
On Mon, Feb 14, 2011 at 12:48 AM, Fujii Masao <masao.fujii@gmail.com> wrote:
> On Sat, Feb 12, 2011 at 8:58 AM, Daniel Farina <daniel@heroku.com> wrote:
>> Context diff equivalent attached.
>
> Thanks for the patch!
>
> As I said before, the timeout which this patch provides doesn't work well
> when the walsender gets blocked in sending WAL. At first, we would
> need to implement a non-blocking write function as an infrastructure
> of the replication timeout, I think.
> http://archives.postgresql.org/message-id/AANLkTi%3DPu2ne%3DVO-%2BCLMXLQh9y85qumLCbBP15CjnyUS%40mail.gmail.com

Interesting point...if that's accepted as required-for-commit, what
are the perceptions of the odds that, presuming I can write the code
quickly enough, that there's enough infrastructure/ports already in
postgres to allow for a non-blocking write on all our supported
platforms?

--
fdr


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Scheduled maintenance affecting gitmaster
Next
From: Andrew Dunstan
Date:
Subject: Re: sepgsql contrib module