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 23:24:43 +0200
Message-ID: <44625A1B.7080809@network-inventory.de> (raw)
In-Reply-To: <1147294882.9755.55.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>
<446252E8.8000304@network-inventory.de>
<1147294882.9755.55.camel@state.g2switchworks.com>
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
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: <44625A1B.7080809@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