On Sun, Jun 14, 2015 at 6:31 PM, Tom Lane <t...@sss.pgh.pa.us> wrote:
> 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. > Good to hear. > 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 ... > I don't think there's a problem with non-blocking I/O and SSL per se, the question is about the .NET TLS/SSL implementation Npgsql uses - so it's really totally unrelated to PostgreSQL... Shay
