On 2014-09-02 17:21:03 -0400, Tom Lane wrote:
> Heikki Linnakangas <hlinnakan...@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.


In my prototype I've changed the API that errors set both
READABLE/WRITABLE. Seems to work....


Andres Freund

 Andres Freund                     http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:

Reply via email to