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
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
ECTED]
[mailto:[EMAIL PROTECTED]] 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, T
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
Scott Marlowe wrote:
On Wed, 2006-05-10 at 04:55, Thomas Vatter wrote:
Tino Wildenhain wrote:
Thomas Vatter schrieb:
is there a possibility for creating views or temp tables in memory to
avoid disk io when user makes select operations
Tino Wildenhain wrote:
Thomas Vatter schrieb:
Tino Wildenhain wrote:
...
Well you will need the equally 40 seconds to fill your hypothetical
in memory table. (even a bit more due to the creation of a
datastructure).
So you can do the aproaches of semi materialized views (that are in
Tino Wildenhain wrote:
Thomas Vatter schrieb:
Tino Wildenhain wrote:
Thomas Vatter schrieb:
is there a possibility for creating views or temp tables in memory
to avoid disk io when user makes select operations?
No need. The data will be available in OS and database caches if
they are
Tino Wildenhain wrote:
Thomas Vatter schrieb:
is there a possibility for creating views or temp tables in memory to
avoid disk io when user makes select operations?
No need. The data will be available in OS and database caches if
they are really required often. If not, tune up the caches
is there a possibility for creating views or temp tables in memory to
avoid disk io when user makes select operations?
regards
tom
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index
