pgjdbc/pgjdbc GitHub issues and pull requests (mirror)  

help / color / mirror / Atom feed

From: helloJosh (@helloJosh) <[email protected]>
To: pgjdbc/pgjdbc <[email protected]>
Subject: Re: [pgjdbc/pgjdbc] PR #3870: feat: Add INFO log when fetchSize is ignored under autocommit=true
Date: Tue, 25 Nov 2025 13:23:03 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

Thanks for the helpful feedback. I understand your concern now - there are far more queries that return only a small number of rows than those that actually cause OOM.

For option(b), I also think choosing a meaningful row-count is difficult, since too many rows are subjective and depends on local memory.

Following your idea in (a), what do you think about the following behavior for a property `stabilityIssues=ignore|warn|fail`

- When set to ignore (the default), pgjdbc would not do anything (current behavior).
- When set to warn, pgjdbc would log a warning when a stability issue is detected (for example, fetchSize > 0 together with autocommit=true).
- When set to fail, pgjdbc would throw an exception (or possibly log at a higher severity), so users can immediately see that a problematic pattern is being used.

view thread (7+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: github://pgjdbc/pgjdbc
  Cc: [email protected], [email protected]
  Subject: Re: [pgjdbc/pgjdbc] PR #3870: feat: Add INFO log when fetchSize is ignored under autocommit=true
  In-Reply-To: <<[email protected]>>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox