pgjdbc/pgjdbc GitHub issues and pull requests (mirror)  

help / color / mirror / Atom feed

From: vlsi (@vlsi) <[email protected]>
To: pgjdbc/pgjdbc <[email protected]>
Subject: Re: [pgjdbc/pgjdbc] issue #3483: Support adaptive fetching without enforcing memory limits, and/or have a separate buffer size for it
Date: Fri, 17 Jan 2025 09:36:31 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

>>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.)

Imagine we don't fully consume the data from the socket.
Imagine user executes yet another "prepare statement / execute call".
We can't multiplex over the single connection, so we would have to consume and buffer the leftover in that case.

>buffer size management in the first place

The core there is to reduce the number of network roundtrips (==avoid `fetch 1` for `.next()`), and we don't want run into "fetch everything in a single go" scenario as well as it might degrade to "buffer everything" in cases like "running extra query while processing the resultset"

view thread (20+ 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] issue #3483: Support adaptive fetching without enforcing memory limits, and/or have a separate buffer size for it
  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