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 99AEB9FA32D
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Wed, 10 May 2006 12:40:54 -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 21704-01
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Wed, 10 May 2006 12:40:48 -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 286249FA3A6
	for <pgsql-performance@postgresql.org>;
	Wed, 10 May 2006 12:40: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 8350350C72A;
	Wed, 10 May 2006 17:39:09 +0200 (CEST)
Message-ID: <4462098D.2010500@network-inventory.de>
Date: Wed, 10 May 2006 17:41:01 +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>
In-Reply-To: <1147273917.9755.22.camel@state.g2switchworks.com>
Content-Type: multipart/alternative;
	boundary="------------040800040001030901050508"
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200605/260
X-Sequence-Number: 19047

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

Scott Marlowe wrote:

>On Wed, 2006-05-10 at 04:55, Thomas Vatter wrote:
>  
>
>>Tino Wildenhain wrote:
>>
>>    
>>
>>>Thomas Vatter schrieb:
>>>
>>>      
>>>
>>>>is there a possibility for creating views or temp tables in memory to 
>>>>avoid disk io when user makes select operations?
>>>>        
>>>>
>>>No need. The data will be available in OS and database caches if
>>>they are really required often. If not, tune up the caches and
>>>do a regular "pre select".
>>>
>>>Regards
>>>Tino
>>>
>>>
>>>      
>>>
>>hmm, I am selecting a resultset with 1300 rows joined from 12 tables. 
>>with jdbc I am waiting 40 seconds until the first row appears. The 
>>following rows appear really fast but the 40 seconds are a problem.
>>    
>>
>
>Are you selecting the whole set at once?  Or are you placing it into a
>cursor?
>
>What happens if you do this by declaring it as a cursor and then
>fetching the first row?
>
>---------------------------(end of broadcast)---------------------------
>TIP 4: Have you searched our list archives?
>
>               http://archives.postgresql.org
>
>
>  
>

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

regards
tom


--------------040800040001030901050508
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">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Scott Marlowe wrote:
<blockquote cite="mid1147273917.9755.22.camel@state.g2switchworks.com"
 type="cite">
  <pre wrap="">On Wed, 2006-05-10 at 04:55, Thomas Vatter wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">Tino Wildenhain wrote:

    </pre>
    <blockquote type="cite">
      <pre wrap="">Thomas Vatter schrieb:

      </pre>
      <blockquote type="cite">
        <pre wrap="">is there a possibility for creating views or temp tables in memory to 
avoid disk io when user makes select operations?
        </pre>
      </blockquote>
      <pre wrap="">
No need. The data will be available in OS and database caches if
they are really required often. If not, tune up the caches and
do a regular "pre select".

Regards
Tino


      </pre>
    </blockquote>
    <pre wrap="">hmm, I am selecting a resultset with 1300 rows joined from 12 tables. 
with jdbc I am waiting 40 seconds until the first row appears. The 
following rows appear really fast but the 40 seconds are a problem.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Are you selecting the whole set at once?  Or are you placing it into a
cursor?

What happens if you do this by declaring it as a cursor and then
fetching the first row?

---------------------------(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>
<br>
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<br>
<br>
regards<br>
tom<br>
<br>
<pre class="moz-signature" cols="72">
</pre>
</body>
</html>

--------------040800040001030901050508--