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 13EBE9FA293
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Wed, 10 May 2006 18:24:38 -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 31938-10
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Wed, 10 May 2006 18:24:31 -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 C7FC89FA2CB
	for <pgsql-performance@postgresql.org>;
	Wed, 10 May 2006 18:24:30 -0300 (ADT)
Received: from [192.168.115.250] (e178173057.adsl.alicedsl.de [85.178.173.57])
	by h57078.serverkompetenz.net (Postfix) with ESMTP id 49B0350C741;
	Wed, 10 May 2006 23:22:50 +0200 (CEST)
Message-ID: <44625A1B.7080809@network-inventory.de>
Date: Wed, 10 May 2006 23:24:43 +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>	
	<446252E8.8000304@network-inventory.de>
	<1147294882.9755.55.camel@state.g2switchworks.com>
In-Reply-To: <1147294882.9755.55.camel@state.g2switchworks.com>
Content-Type: multipart/alternative;
	boundary="------------080300010005000406030103"
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200605/275
X-Sequence-Number: 19062

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

Scott Marlowe wrote:

>On Wed, 2006-05-10 at 15:54, Thomas Vatter wrote:
>
>  
>
>>>  
>>>      
>>>
>>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?
>>    
>>
>
>Not sure.  I don't use a lot of prepared statements.  I tend to build
>queries and throw the at the database.  In that instance, it's done
>like:
>
>create cursor cursorname as select (rest of query here);
>fetch from cursorname;
>
>You can find more on cursors here:
>
>http://www.postgresql.org/docs/8.1/interactive/sql-declare.html
>
>Not sure if you can use them with prepared statements, or if prepared
>statements have their own kind of implementation.
>
>---------------------------(end of broadcast)---------------------------
>TIP 6: explain analyze is your friend
>
>
>  
>

Yes, I have used embedded sql and create cursor, fetch before I started 
with jdbc, seems that
I have to find out if new jdbc has a better way than simply resultSet = 
statement.executeQuery().

regards
tom


--------------080300010005000406030103
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="mid1147294882.9755.55.camel@state.g2switchworks.com"
 type="cite">
  <pre wrap="">On Wed, 2006-05-10 at 15:54, Thomas Vatter wrote:

  </pre>
  <blockquote type="cite">
    <blockquote type="cite">
      <pre wrap="">  
      </pre>
    </blockquote>
    <pre wrap="">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?
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Not sure.  I don't use a lot of prepared statements.  I tend to build
queries and throw the at the database.  In that instance, it's done
like:

create cursor cursorname as select (rest of query here);
fetch from cursorname;

You can find more on cursors here:

<a class="moz-txt-link-freetext" href="http://www.postgresql.org/docs/8.1/interactive/sql-declare.html">http://www.postgresql.org/docs/8.1/interactive/sql-declare.html</a>

Not sure if you can use them with prepared statements, or if prepared
statements have their own kind of implementation.

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend


  </pre>
</blockquote>
<br>
Yes, I have used embedded sql and create cursor, fetch before I started
with jdbc, seems that<br>
I have to find out if new jdbc has a better way than simply resultSet =
statement.executeQuery().<br>
<br>
regards<br>
tom<br>
<br>
<pre class="moz-signature" cols="72">
</pre>
</body>
</html>

--------------080300010005000406030103--