From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Replication server timeout patch |
Date: | 2011-03-06 14:10:51 |
Message-ID: | AANLkTi=BuEf70OTciUnPQ0DO1j3n-Zp9+aaNN1TTvxwc@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Mar 6, 2011 at 5:03 PM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
>> Why does internal_flush_if_writable compute bufptr differently from
>> internal_flush? And shouldn't it be static?
>>
>> It seems to me that this ought to be refactored so that you don't
>> duplicate so much code. Maybe static int internal_flush(bool
>> nonblocking).
>>
>> I don't think that the while (bufptr < bufend) loop needs to contain
>> the code to set and clear the nonblocking state. You could do the
>> whole loop with nonblocking mode turned on and then reenable it just
>> once at the end. Besides possibly being clearer, that would be more
>> efficient and leave less room for unexpected failures.
>
> All these comments seem to make sense. Will fix. Thanks!
Done. I attached the updated patch.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
Attachment | Content-Type | Size |
---|---|---|
replication_timeout_v4.patch | text/x-diff | 45.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2011-03-06 14:26:22 | Re: Sync Rep v19 |
Previous Message | Jan Urbański | 2011-03-06 12:14:48 | Re: pl/python tracebacks |