pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Thomas Vatter <thomas.vatter@network-inventory.de>
To: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: Tino Wildenhain <tino@wildenhain.de>
Cc: pgsql-performance@postgresql.org
Subject: Re: in memory views
Date: Wed, 10 May 2006 22:54:00 +0200
Message-ID: <446252E8.8000304@network-inventory.de> (raw)
In-Reply-To: <1147275906.9755.25.camel@state.g2switchworks.com>
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>

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

view thread (19+ messages)  latest in thread

Message-ID: <446252E8.8000304@network-inventory.de>
Permalink:  ../446252E8.8000304@network-inventory.de/
Also on:    postgresql.org/message-id/446252E8.8000304@network-inventory.de

 · 

reply

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-performance@postgresql.org
  Cc: thomas.vatter@network-inventory.de, smarlowe@g2switchworks.com, tino@wildenhain.de
  Subject: Re: in memory views
  In-Reply-To: <446252E8.8000304@network-inventory.de>

* 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