Does postgres cache the entire result set before it begins returning
data to the client?
I have a table with ~8 million rows and I am executing a query which
should return about ~800,000 rows. The problem is that as soon as I
execute the query it absolutely kills my machine and begins swapping
On Mon, 13 Sep 2004 21:11:07 -0400, Tom Lane [EMAIL PROTECTED] wrote:
Stephen Crowley [EMAIL PROTECTED] writes:
Does postgres cache the entire result set before it begins returning
data to the client?
The backend doesn't, but libpq does, and I think JDBC does too.
I'd recommend using
:
Stephen Crowley [EMAIL PROTECTED] writes:
On Mon, 13 Sep 2004 21:11:07 -0400, Tom Lane [EMAIL PROTECTED] wrote:
Stephen Crowley [EMAIL PROTECTED] writes:
Does postgres cache the entire result set before it begins returning
data to the client?
The backend doesn't, but libpq does, and I think
would the fact that it needs to be vaccumed cause such a huge
hit in performance? When i vacuumed it did free up nearly 25% of the
space.
--Stephen
On Fri, 17 Sep 2004 22:44:05 +0200, Manfred Koizar [EMAIL PROTECTED] wrote:
On Thu, 16 Sep 2004 20:51:11 -0500, Stephen Crowley
[EMAIL PROTECTED] wrote
Thanks for the explanation. So what sort of changes need to be made to
the client/server protocol to fix this problem?
On Thu, 23 Sep 2004 18:22:15 -0500 (EST), Kris Jurka [EMAIL PROTECTED] wrote:
On Tue, 14 Sep 2004, Stephen Crowley wrote:
Problem solved.. I set the fetchSize