Re: ResultSet memory usage

From: "Dave Cramer" <Dave(at)micro-automation(dot)net>
To: "'Timo Savola'" <timo(dot)savola(at)codeonline(dot)com>, <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: ResultSet memory usage
Date: 2002-01-11 16:22:27
Message-ID: 00e101c19abc$29a198f0$c201a8c0@inspiron
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Hmmm... I'm not exactly sure what postgres would do with a blocked
socket, but yes I suppose it could be.

Cursors work just fine in this instance, though

Dave

-----Original Message-----
From: pgsql-jdbc-owner(at)postgresql(dot)org
[mailto:pgsql-jdbc-owner(at)postgresql(dot)org] On Behalf Of Timo Savola
Sent: Friday, January 11, 2002 11:08 AM
To: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: [JDBC] ResultSet memory usage

> Unfortunately this is an artifact of the way the backend works, once
> the request is made the backend is going to give us all the data.

Couldn't that still be implemented in the JDBC driver by reading from
the socket a little at a time? Or would that introduce bigger problems,
like catastrophic slowdown of other connections to the backend?

Timo

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Ross J. Reedstrom 2002-01-11 16:38:23 Re: ResultSet memory usage
Previous Message Timo Savola 2002-01-11 16:08:23 Re: ResultSet memory usage