Message-ID: <gh-pgjdbc-pgjdbc-3483-c2597786274@github.com>
From: "davecramer (@davecramer)" <noreply+davecramer@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Fri, 17 Jan 2025 09:21:40 +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: davecramer
X-GitHub-Comment-Id: 2597786274
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-2597786274
Content-Type: text/plain; charset=utf-8

> (One other final, somewhat unrelated thought.... I have wondered why the ResultSet buffering is really necessary in the first place... couldn't the `ResultSet.next` function stream the rows directly from the TCP socket without significant buffering? This would avoid the whole issue of buffer size management in the first place.)

This would be the best solution. Have a look at https://github.com/pgjdbc/pgjdbc/pull/1735 see if it is reviveable