Message-ID: <gh-pgjdbc-pgjdbc-2656-c1301332180@github.com>
From: "mirraj2 (@mirraj2)" <noreply+mirraj2@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Wed, 02 Nov 2022 21:41:07 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #2656: Adaptive Fetch doesn't enable ResultSet streaming
In-Reply-To: <gh-pgjdbc-pgjdbc-2656@github.com>
References: <gh-pgjdbc-pgjdbc-2656@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: mirraj2
X-GitHub-Comment-Id: 1301332180
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 2656
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/2656#issuecomment-1301332180
Content-Type: text/plain; charset=utf-8

@davecramer - the code you pasted demonstrates what I verified _does_ work correctly.  If you setFetchSize() on the Statement it will work.  The bug is not about setFetchSize().  It is about using the "adaptiveFetch" feature.  AdaptiveFetch should automatically change the fetch size based on the size of each row.

To test what I'm seeing, comment out the "setFetchSize" row, and use something like the following connection string:
jdbc:postgresql://localhost:5432/test?adaptiveFetch=true&defaultRowFetchSize=10&maxResultBuffer=128M

I would urge you to set these parameters via the connection string instead of via Properties, because maybe the bug has to do with settings via the query string.