Message-ID: <gh-pgjdbc-pgjdbc-3870-c3575845249@github.com>
From: "helloJosh (@helloJosh)" <noreply+helloJosh@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Tue, 25 Nov 2025 14:10:05 +0000
Subject: Re: [pgjdbc/pgjdbc] PR #3870: feat: Add INFO log when fetchSize is ignored under autocommit=true
In-Reply-To: <gh-pgjdbc-pgjdbc-3870@github.com>
References: <gh-pgjdbc-pgjdbc-3870@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: helloJosh
X-GitHub-Comment-Id: 3575845249
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3870
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/3870#issuecomment-3575845249
Content-Type: text/plain; charset=utf-8

First, I also thought this could be addressed in Spring Batch. But the difficulty is that Spring would have to apply the same logic consistently across all other JDBC-based components as well. That's why I ended up contributing an update to the Spring Batch documentation instead.

Also, I think Spring can't fully detect or explain this behavior. Because fetchSize and server-side cursor is determined by the JDBC driver.

In my view pgjdbc is the best place to provide a precise diagnostic signal when fetchSize > 0 is combined with autocommit=true.