pgjdbc/pgjdbc GitHub issues and pull requests (mirror)
help / color / mirror / Atom feedFrom: davecramer (@davecramer) <[email protected]>
To: pgjdbc/pgjdbc <[email protected]>
Subject: Re: [pgjdbc/pgjdbc] issue #2918: Set defaultRowFetchSize=10000 by default to improve app stability
Date: Thu, 04 Sep 2025 15:03:26 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
> I'd rather have a "safer" value in the ballpark of 128, and if that's too low for you, 1000 max, but nowhere above that. Currently pgJDBC eats RAM like it's unlimited. I would like that just as much as you do, but it isn't ;)
>
> Also, why not honor the fetchSize on every SELECT statement regardless of auto-commit ?
>
> Auto-commit should only affect writing statements (INSERT/UPDATE/DELETE), not read (SELECT) statements, right ? Why is auto-commit even relevant to honoring the fetchSize in the first place ? I'm confused.
This is an artifact of MVCC. You need to be in a transaction to create a snapshot to make sure that the data is consistent between fetches
view thread (18+ messages)
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] issue #2918: Set defaultRowFetchSize=10000 by default to improve app stability
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