Message-ID: <gh-pgjdbc-pgjdbc-3996-c4111717844@github.com>
From: "vlsi (@vlsi)" <noreply+vlsi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Mon, 23 Mar 2026 15:57:38 +0000
Subject: Re: [pgjdbc/pgjdbc] PR #3996: fix: enable cursor-based fetching in extended protocol when transaction started via SQL command
In-Reply-To: <gh-pgjdbc-pgjdbc-3996@github.com>
References: <gh-pgjdbc-pgjdbc-3996@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: vlsi
X-GitHub-Comment-Id: 4111717844
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3996
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/3996#issuecomment-4111717844
Content-Type: text/plain; charset=utf-8

I am not following your question.
There's a valid API use, and currently it skips using cursor (==It loads everything at once in a single go).
As far as I understand, the code wants to skip cursor in certain cases so the cursor does not disappear mid-fetch.

The condition for "use vs not use" the cursor was not quite right, so the condition could be lifted.

I don't understand how your question maps to the test case at hand