| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, robertmhaas(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Escaping from blocked send() reprised. |
| Date: | 2014-09-02 21:23:58 |
| Message-ID: | 20140902212358.GF28635@awork2.anarazel.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2014-09-02 17:21:03 -0400, Tom Lane wrote:
> Heikki Linnakangas <hlinnakangas(at)vmware(dot)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....
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 2014-09-02 21:32:20 | Re: PL/pgSQL 2 |
| Previous Message | Jan Wieck | 2014-09-02 21:23:26 | Re: PL/pgSQL 2 |