On 09/03/2014 12:23 AM, Andres Freund wrote:
> On 2014-09-02 17:21:03 -0400, Tom Lane wrote:
>> Heikki Linnakangas <hlinnakangas@vmware.com> writes:
>>> I was going to suggest using WaitLatchOrSocket instead of sleeping in 1
>>> second increment, but I see that WaitLatchOrSocket() doesn't currently
>>> support waiting for a socket to become writeable, without also waiting
>>> for it to become readable. I wonder how difficult it would be to lift
>>> that restriction.
>>
>> My recollection is that there was a reason for that, but I don't recall
>> details any more.
>
> http://git.postgresql.org/pg/commitdiff/e42a21b9e6c9b9e6346a34b62628d48ff2fc6ddf
>
> In my prototype I've changed the API that errors set both
> READABLE/WRITABLE. Seems to work....
Andres, would you mind posting the WIP patch you have? That could be a
better foundation for this patch.
- Heikki