Message-ID: <gh-pgjdbc-pgjdbc-2325-c4141928218@github.com>
From: "beikov (@beikov)" <noreply+beikov@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Fri, 27 Mar 2026 11:25:14 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #2325: Support pipelining queries
In-Reply-To: <gh-pgjdbc-pgjdbc-2325@github.com>
References: <gh-pgjdbc-pgjdbc-2325@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: beikov
X-GitHub-Comment-Id: 4141928218
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-4141928218
Content-Type: text/plain; charset=utf-8

I could try to remodel it to also work with regular threads, but sharing a connection between different non-virtual threads didn't seem like a good idea to me, whereas with virtual threads it feels more natural.

Are there any good use cases for doing pipelining this way with platform threads? I would think that for non-virtual thread users it would be much more convenient to use the JDBC batch API for pipelining instead. Wdyt?