| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Thomas Vatter <thomas(dot)vatter(at)network-inventory(dot)de> |
| Cc: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com>, Tino Wildenhain <tino(at)wildenhain(dot)de>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: in memory views |
| Date: | 2006-05-10 22:16:23 |
| Message-ID: | Pine.BSO.4.63.0605101715020.26920@leary2.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2006-05-10 22:19:49 | Re: UNSUBSCRIBE |
| Previous Message | Jim C. Nasby | 2006-05-10 22:10:48 | Re: Lot'sa joins - performance tip-up, please? |