Simon Riggs wrote:
> As we know from recent versions, the JDBC driver can deadlock. We also
> know that the deadlock detector as exists does not detect all types of
> deadlock and isn't foolproof at that either. Not criticism, just
> summarising.
Do you mean the potential read-write socket deadlock (where we're
blocked on write waiting for the server to consume some data, but it's
blocked waiting for us to consume some data), or something else?
-O