From: | Thomas Vatter <thomas(dot)vatter(at)network-inventory(dot)de> |
---|---|
To: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
Cc: | Tino Wildenhain <tino(at)wildenhain(dot)de>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: in memory views |
Date: | 2006-05-10 15:41:01 |
Message-ID: | 4462098D.2010500@network-inventory.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
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?
>>>>
>>>>
>>>No need. The data will be available in OS and database caches if
>>>they are really required often. If not, tune up the caches and
>>>do a regular "pre select".
>>>
>>>Regards
>>>Tino
>>>
>>>
>>>
>>>
>>hmm, I am selecting a resultset with 1300 rows joined from 12 tables.
>>with jdbc I am waiting 40 seconds until the first row appears. The
>>following rows appear really fast but the 40 seconds are a problem.
>>
>>
>
>Are you selecting the whole set at once? Or are you placing it into a
>cursor?
>
>What happens if you do this by declaring it as a cursor and then
>fetching the first row?
>
>---------------------------(end of broadcast)---------------------------
>TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
>
>
>
>
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
regards
tom
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2006-05-10 15:45:06 | Re: in memory views |
Previous Message | Nis Jorgensen | 2006-05-10 15:30:07 | Re: [HACKERS] Big IN() clauses etc : feature proposal |