From: Thomas Kellerer <spam_eater@gmx.net>
To: pgsql-sql@postgresql.org
Subject: Re: SELECT very slow
Date: Thu, 16 Jun 2005 17:33:19 +0200
Message-ID: <d8s5q1$5ud$1@sea.gmane.org> (raw)
In-Reply-To: <op.ssgyniecth1vuj@localhost>
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>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: spam_eater@gmx.net
Subject: Re: SELECT very slow
In-Reply-To: <d8s5q1$5ud$1@sea.gmane.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox