X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org
Received: from localhost (mx1.hub.org [200.46.208.251])
	by postgresql.org (Postfix) with ESMTP id 39A0C9FA38E
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Wed, 10 May 2006 17:53:58 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024)
	with ESMTP id 24825-03
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Wed, 10 May 2006 17:53:49 -0300 (ADT)
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from h57078.serverkompetenz.net (talk-net.net [81.169.128.8])
	by postgresql.org (Postfix) with ESMTP id E66F99FA293
	for <pgsql-performance@postgresql.org>;
	Wed, 10 May 2006 17:53:48 -0300 (ADT)
Received: from [192.168.115.250] (e178173057.adsl.alicedsl.de [85.178.173.57])
	by h57078.serverkompetenz.net (Postfix) with ESMTP id 043B750C77D;
	Wed, 10 May 2006 22:52:06 +0200 (CEST)
Message-ID: <446252E8.8000304@network-inventory.de>
Date: Wed, 10 May 2006 22:54:00 +0200
From: Thomas Vatter <thomas.vatter@network-inventory.de>
User-Agent: Mozilla Thunderbird 1.0.5 (Windows/20050711)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Scott Marlowe <smarlowe@g2switchworks.com>
CC: Tino Wildenhain <tino@wildenhain.de>,
 pgsql-performance@postgresql.org
Subject: Re: in memory views
References: <4461AFFF.7060200@network-inventory.de>	
	<4461B3DE.6030700@wildenhain.de>
	<4461B899.4030502@network-inventory.de>	
	<1147273917.9755.22.camel@state.g2switchworks.com>	
	<4462098D.2010500@network-inventory.de>
	<1147275906.9755.25.camel@state.g2switchworks.com>
In-Reply-To: <1147275906.9755.25.camel@state.g2switchworks.com>
Content-Type: multipart/alternative;
	boundary="------------030109030204080602000009"
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200605/271
X-Sequence-Number: 19058

This is a multi-part message in MIME format.
--------------030109030204080602000009
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Scott Marlowe wrote:

>On Wed, 2006-05-10 at 10:41, Thomas Vatter wrote:
>  
>
>>Scott Marlowe wrote: 
>>    
>>
>
>  
>
>>>What happens if you do this by declaring it as a cursor and then
>>>fetching the first row?
>>>      
>>>
>
>  
>
>>>  
>>>      
>>>
>>I do executeQuery(), for the resultSet I do next() and return one row,
>>but wait, I have to review the logic in this area, I can tell you
>>tomorrow
>>    
>>
>
>
>A good short test is to run explain analyze on the query from the psql
>command line.  If it shows an execution time of significantly less than
>what you get from you application, then it is likely that the real
>problem is that your application is receiving the whole result set via
>libpq and waiting for that.  A cursor will solve that problem.
>
>---------------------------(end of broadcast)---------------------------
>TIP 4: Have you searched our list archives?
>
>               http://archives.postgresql.org
>
>
>  
>
Yes, the difference between psql command line and application is 6 
seconds to 40 seconds. It is
exactly the step resultSet = excecuteQuery() that needs 40 seconds. I 
use next() as a cursor
through the resultSet, but I fear this is not enough, do I have to use 
createStatement(resultSetType,
resultSetConcurrency) respectively prepareStatement (resultSetType, 
resultSetConcurrency) to
achieve the cursor behaviour?

regards
tom


--------------030109030204080602000009
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Scott Marlowe wrote:
<blockquote cite="mid1147275906.9755.25.camel@state.g2switchworks.com"
 type="cite">
  <pre wrap="">On Wed, 2006-05-10 at 10:41, Thomas Vatter wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">Scott Marlowe wrote: 
    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
  <blockquote type="cite">
    <blockquote type="cite">
      <pre wrap="">What happens if you do this by declaring it as a cursor and then
fetching the first row?
      </pre>
    </blockquote>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
  <blockquote type="cite">
    <blockquote type="cite">
      <pre wrap="">  
      </pre>
    </blockquote>
    <pre wrap="">I do executeQuery(), for the resultSet I do next() and return one row,
but wait, I have to review the logic in this area, I can tell you
tomorrow
    </pre>
  </blockquote>
  <pre wrap=""><!---->

A good short test is to run explain analyze on the query from the psql
command line.  If it shows an execution time of significantly less than
what you get from you application, then it is likely that the real
problem is that your application is receiving the whole result set via
libpq and waiting for that.  A cursor will solve that problem.

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

               <a class="moz-txt-link-freetext" href="http://archives.postgresql.org">http://archives.postgresql.org</a>


  </pre>
</blockquote>
Yes, the difference between psql command line and application is 6
seconds to 40 seconds. It is<br>
exactly the step resultSet = excecuteQuery() that needs 40 seconds. I
use next() as a cursor<br>
through the resultSet, but I fear this is not enough, do I have to use
createStatement(resultSetType, <br>
resultSetConcurrency) respectively prepareStatement (resultSetType,
resultSetConcurrency) to<br>
achieve the cursor behaviour?<br>
<br>
regards<br>
tom<br>
<br>
</body>
</html>

--------------030109030204080602000009--