pgjdbc/pgjdbc GitHub issues and pull requests (mirror)
help / color / mirror / Atom feedFrom: davecramer (@davecramer) <[email protected]>
To: pgjdbc/pgjdbc <[email protected]>
Subject: Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
Date: Wed, 22 Jan 2020 10:49:22 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
On Wed, Jan 22, 2020, 12:59 AM Craig Ringer, <[email protected]>
wrote:
> I increasingly think I need to find the time to make PgJDBC use separate
> threads for tx and rx so the method-caller's thread can retain control.
> PgJDBC can then wait on multiple events in possible deadlock scenarios,
> i.e. "when tx buffer is full, sleep until tx buffer writeable OR rx buffer
> readable".
>
> Shouldn't even be that hard.
>
> —
> You are receiving this because you were assigned.
> Reply to this email directly, view it on GitHub
> <https://github.com/pgjdbc/pgjdbc/issues/194?email_source=notifications&email_token=AADDH5QB2EQ46...;,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AADDH5QLSB6FLM44UHGDY7LQ67OFDANCNFSM4AVH6IZQ;
> .
>
I have to agree. There are other good reasons to do this as well such as
the issues we run into in the replication protocol with socket timeouts
+1 from me
>
view thread (36+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: github://pgjdbc/pgjdbc
Cc: [email protected], [email protected]
Subject: Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
In-Reply-To: <<[email protected]>>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox