Message-ID: <gh-pgjdbc-pgjdbc-2918-c1633058442@github.com>
From: "lure (@lure)" <noreply+lure@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Wed, 12 Jul 2023 19:03:34 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #2918: Set defaultRowFetchSize=10000 by default to improve app stability
In-Reply-To: <gh-pgjdbc-pgjdbc-2918@github.com>
References: <gh-pgjdbc-pgjdbc-2918@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: lure
X-GitHub-Comment-Id: 1633058442
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 2918
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/2918#issuecomment-1633058442
Content-Type: text/plain; charset=utf-8

> that information is not conveyed. Seems like a bug in the server.

After some consideration and reading, it might not be a bug. The intermediate operations "see" only the rows passed to them. the generatedKeys result set holds the reference to the cursor, which allows it to read remaining records from the server. Initial set contains just the FetchSize number of rows. 

So, unless there are changes to /capabilities of PG protocol that could be used to request the affected row count after the generated keys are parsed, we are probably stuck