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

Re: in memory views

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

In response to

Responses

pgsql-performance by date

Next:From: Dave DutcherDate: 2006-05-10 21:08:49
Subject: Re: in memory views
Previous:From: Thomas VatterDate: 2006-05-10 20:54:00
Subject: Re: in memory views

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