Shay Rojansky <r...@roji.org> writes:
> [ rely on non-blocking sockets to avoid deadlock ]
Yeah, that's pretty much the approach libpq has taken: write (or read)
when you can, but press on when you can't.
> The main issue I'm concerned about
> is SSL/TLS, which is a layer on top of the sockets and which might not work
> well with non-blocking sockets...
We have not had word of any such problem with libpq. It's possible that
the intersection of SSL users with non-blocking-mode users is nil, but
I kinda doubt that. You do need to interpret openssl's return codes
correctly ...
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
