pgjdbc/pgjdbc GitHub issues and pull requests (mirror)  

help / color / mirror / Atom feed

From: mschorsch (@mschorsch) <[email protected]>
To: pgjdbc/pgjdbc <[email protected]>
Subject: Re: [pgjdbc/pgjdbc] issue #3835: Virtual Thread pinned in PostgreSQL JDBC Driver 42.7.8
Date: Sat, 18 Oct 2025 07:51:08 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

Hi @vlsi, sorry for the late reply. 

> Do you have a reproducer for the issue?

I do not have a reproducer. We were only able to find the problem in production.

> QueryExecutorBase.getStandardConformingStrings acquires a connection-scoped lock, so if you got pinning, then it looks like the same connection was used in a different thread which looks like an anti-pattern.

Thanks for the hint. We will check that again.

> In any case, it makes sense to move createAction.create() out of the synchronized block, however, I believe it will just mask the true issue of "sharing the same connection between concurrent execute threads" which you probably need to address in the app.

👍

view thread (7+ 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 #3835: Virtual Thread pinned in PostgreSQL JDBC Driver 42.7.8
  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