To: "Thomas Kellerer" <spam_eater@gmx.net>, pgsql-sql@postgresql.org
Subject: Re: SELECT very slow
References: <d87ood$8vq$1@sea.gmane.org> <d8s30h$r12$1@sea.gmane.org>
	<1118930439.3382.91.camel@state.g2switchworks.com>
	<d8q8iq$pfg$1@sea.gmane.org> <op.ssfgo6xath1vuj@localhost>
	<op.ssc0t7wrth1vuj@localhost> <d8pqbi$a5q$1@sea.gmane.org>
Message-ID: <op.ssgyniecth1vuj@localhost>
Date: Thu, 16 Jun 2005 17:29:32 +0200
From: PFC <lists@boutiquenumerique.com>
Organization: =?iso-8859-15?Q?La_Boutique_Num=E9rique?=
Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
In-Reply-To: <d8s30h$r12$1@sea.gmane.org>
User-Agent: Opera M2(BETA2)/8.0 (Linux, build 987)


> If autocommit is on (or fetch size is zero) then the driver will build  
> the whole
> result set before returning to the caller.

	Sure, but that is not your problem : even building the whole result set  
should not take longer than a few seconds (I gave you test timings in a  
previous message).
	So... what ?
	What does the taskman say ? CPU at 100% ? how much kernel time ?

>
> http://jdbc.postgresql.org/documentation/80/query.html#query-with-cursor
>
> Thomas
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>