Message-ID: From: "vlsi (@vlsi)" To: "pgjdbc/pgjdbc" Date: Fri, 27 Mar 2026 16:55:57 +0000 Subject: Re: [pgjdbc/pgjdbc] issue #2325: Support pipelining queries In-Reply-To: References: List-Id: X-GitHub-Author-Login: vlsi X-GitHub-Comment-Id: 4143971542 X-GitHub-Comment-Type: issue_comment X-GitHub-Issue: 2325 X-GitHub-Repo: pgjdbc/pgjdbc X-GitHub-Type: comment X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/2325#issuecomment-4143971542 Content-Type: text/plain; charset=utf-8 > 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.