pgjdbc/pgjdbc GitHub issues and pull requests (mirror)
help / color / mirror / Atom feedFrom: vlsi (@vlsi) <[email protected]>
To: pgjdbc/pgjdbc <[email protected]>
Subject: Re: [pgjdbc/pgjdbc] issue #2325: Support pipelining queries
Date: Fri, 27 Mar 2026 16:55:57 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
> then I'll test to see if that works as well.
I haven't noticed if you use any virtual thread specific APIs, so it is unclear why you cover the feature with `if (virtual)` check.
> Since virtual threads would usually (always?) run on the same carrier thread, the whole thing is more or less single-threaded
Imagine someone switching their Spring Boot app to virtual threads and saying something like "we don't need connection pool, just pipeline everything through a single connection".
---
Do you know practical ways to test the change?
I wonder what are the limitations and what could theoretically be put in a changelog.
Would it support just `preparedStatement.execute` or all the APIs?
---
Historically, the implementation was not designed for full thread-safety, so mutable fields in `PgConnection` might play against concurrent use of the connection.
view thread (15+ messages)
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 #2325: Support pipelining queries
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