Subject: Re: in memory views
From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Thomas Vatter <thomas.vatter@network-inventory.de>
Cc: Tino Wildenhain <tino@wildenhain.de>, pgsql-performance@postgresql.org
In-Reply-To: <446252E8.8000304@network-inventory.de>
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>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1147294882.9755.55.camel@state.g2switchworks.com>
Mime-Version: 1.0
Date: Wed, 10 May 2006 16:01:22 -0500

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.