Skip site navigation (1) Skip section navigation (2)

Re: in memory views

From: Thomas Vatter <thomas(dot)vatter(at)network-inventory(dot)de>
To: Scott Marlowe <smarlowe(at)g2switchworks(dot)com>
Cc: Tino Wildenhain <tino(at)wildenhain(dot)de>, pgsql-performance(at)postgresql(dot)org
Subject: Re: in memory views
Date: 2006-05-10 21:24:43
Message-ID: 44625A1B.7080809@network-inventory.de (view raw or flat)
Thread:
Lists: pgsql-performance
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

In response to

Responses

pgsql-performance by date

Next:From: Jim C. NasbyDate: 2006-05-10 22:10:48
Subject: Re: Lot'sa joins - performance tip-up, please?
Previous:From: Thomas VatterDate: 2006-05-10 21:18:58
Subject: Re: in memory views

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group