To: pgsql-sql@postgresql.org
From: Thomas Kellerer <spam_eater@gmx.net>
Subject: Re: SELECT very slow
Date: Thu, 16 Jun 2005 17:33:19 +0200
Lines: 19
Message-ID: <d8s5q1$5ud$1@sea.gmane.org>
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>
	<op.ssgyniecth1vuj@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT;
	rv:1.7.6) Gecko/20050319 Mnenhy/0.7.2.0
In-Reply-To: <op.ssgyniecth1vuj@localhost>

On 16.06.2005 17:29 PFC wrote:

>> 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 ?
> 

Taskmanager (I'm on windows) does not show any high CPU usage. And (as I wrote
in the initial post) I cannot see any memory increase in the PG process as well
(which I would expect with a result set of that size built up in memory).

Thomas