From: Thomas Vatter <thomas.vatter@network-inventory.de>
To: Dave Dutcher <dave@tridecap.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: in memory views
Date: Wed, 10 May 2006 23:18:58 +0200
Message-ID: <446258C2.2070805@network-inventory.de> (raw)
In-Reply-To: <01fd01c67475$ef17d530$8300a8c0@tridecap.com>
References: <01fd01c67475$ef17d530$8300a8c0@tridecap.com>
Dave Dutcher wrote:
> Are you using the Postgres JDBC driver? Or are you using an ODBC JDBC
> driver? The Postgres specific driver is usually faster.
I'm using the postgres driver
regards
tom
>
>
>
> -----Original Message-----
> *From:* pgsql-performance-owner@postgresql.org
> [mailto:pgsql-performance-owner@postgresql.org] *On Behalf Of
> *Thomas Vatter
> *Sent:* Wednesday, May 10, 2006 3:54 PM
> *To:* Scott Marlowe
> *Cc:* Tino Wildenhain; pgsql-performance@postgresql.org
> *Subject:* Re: [PERFORM] in memory views
>
> Scott Marlowe wrote:
>
>>On Wed, 2006-05-10 at 10:41, Thomas Vatter wrote:
>>
>>
>>>Scott Marlowe wrote:
>>>
>>>
>>
>>
>>
>>>>What happens if you do this by declaring it as a cursor and then
>>>>fetching the first row?
>>>>
>>>>
>>
>>
>>
>>>>
>>>>
>>>>
>>>I do executeQuery(), for the resultSet I do next() and return one row,
>>>but wait, I have to review the logic in this area, I can tell you
>>>tomorrow
>>>
>>>
>>
>>
>>A good short test is to run explain analyze on the query from the psql
>>command line. If it shows an execution time of significantly less than
>>what you get from you application, then it is likely that the real
>>problem is that your application is receiving the whole result set via
>>libpq and waiting for that. A cursor will solve that problem.
>>
>>---------------------------(end of broadcast)---------------------------
>>TIP 4: Have you searched our list archives?
>>
>> http://archives.postgresql.org
>>
>>
>>
>>
> 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?
>
> regards
> tom
>
--
Mit freundlichen Grüßen / Regards
Vatter
Network Inventory Software
Sun Microsystems Principal Partner
www.network-inventory.de
Tel. 030-79782510
E-Mail thomas.vatter@network-inventory.de
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, dave@tridecap.com
Subject: Re: in memory views
In-Reply-To: <446258C2.2070805@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