pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Thomas Vatter <thomas.vatter@network-inventory.de>
To: Kris Jurka <books@ejurka.com>
Cc: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: Tino Wildenhain <tino@wildenhain.de>
Cc: pgsql-performance@postgresql.org
Subject: Re: in memory views
Date: Thu, 11 May 2006 01:08:00 +0200
Message-ID: <44627250.5010908@network-inventory.de> (raw)
In-Reply-To: <Pine.BSO.4.63.0605101715020.26920@leary2.csoft.net>
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>
	<44625A1B.7080809@network-inventory.de>
	<Pine.BSO.4.63.0605101715020.26920@leary2.csoft.net>

Kris Jurka wrote:

>
>
> On Wed, 10 May 2006, 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?
>
>
> http://jdbc.postgresql.org/documentation/81/query.html#query-with-cursor
>
> Kris Jurka


I was just returning to my mailbox to report success, I was just a bit 
faster than your e-mail,  I have found the fetchSize function, it 
reduces the delay to 6 seconds. thanks a lot to all who helped, this was 
really great support, I am glad that the problem is solved

tom





view thread (19+ messages)

Message-ID: <44627250.5010908@network-inventory.de>
Permalink:  ../44627250.5010908@network-inventory.de/
Also on:    postgresql.org/message-id/44627250.5010908@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, books@ejurka.com, smarlowe@g2switchworks.com, tino@wildenhain.de
  Subject: Re: in memory views
  In-Reply-To: <44627250.5010908@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