Re: ResultSet memory usage
От | Dave Cramer |
---|---|
Тема | Re: ResultSet memory usage |
Дата | |
Msg-id | 00e101c19abc$29a198f0$c201a8c0@inspiron обсуждение исходный текст |
Ответ на | Re: ResultSet memory usage (Timo Savola <timo.savola@codeonline.com>) |
Ответы |
Re: ResultSet memory usage
|
Список | 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 по дате отправления: