Re: ResultSet memory usage - Mailing list pgsql-jdbc

From Dave Cramer
Subject Re: ResultSet memory usage
Date
Msg-id 00e101c19abc$29a198f0$c201a8c0@inspiron
Whole thread Raw
In response to Re: ResultSet memory usage  (Timo Savola <timo.savola@codeonline.com>)
Responses Re: ResultSet memory usage
List 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@postgresql.org
[mailto:pgsql-jdbc-owner@postgresql.org] On Behalf Of Timo Savola
Sent: Friday, January 11, 2002 11:08 AM
To: pgsql-jdbc@postgresql.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@postgresql.org)



pgsql-jdbc by date:

Previous
From: Timo Savola
Date:
Subject: Re: ResultSet memory usage
Next
From: "Ross J. Reedstrom"
Date:
Subject: Re: ResultSet memory usage