Message-ID: <gh-pgjdbc-pgjdbc-3483-c2603413601@github.com>
From: "james-johnston-thumbtack (@james-johnston-thumbtack)" <noreply+james-johnston-thumbtack@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Tue, 21 Jan 2025 00:41:54 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #3483: Support adaptive fetching without enforcing memory limits, and/or have a separate buffer size for it
In-Reply-To: <gh-pgjdbc-pgjdbc-3483@github.com>
References: <gh-pgjdbc-pgjdbc-3483@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: james-johnston-thumbtack
X-GitHub-Comment-Id: 2603413601
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3483
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3483#issuecomment-2603413601
Content-Type: text/plain; charset=utf-8

> I am afraid it might break the semantics: "execute 0" was supposed to fetch all the rows, and the application might assume extra fetches would not be required after "fetch all rows" execute. So I think it might be ok to keep "fetch all" intact.

The main point was just to have a way to specify something like "get me roughly 50 MB at a time" without worrying about row counts at all.  I suppose one can pass a row fetch size of `9999999999` or something like that if row fetch size of `0` were to ignore the requested/proposed byte limit.