| From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
|---|---|
| To: | Thomas Vatter <thomas(dot)vatter(at)network-inventory(dot)de> |
| Cc: | Tino Wildenhain <tino(at)wildenhain(dot)de>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: in memory views |
| Date: | 2006-05-10 15:11:57 |
| Message-ID: | 1147273917.9755.22.camel@state.g2switchworks.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nis Jorgensen | 2006-05-10 15:30:07 | Re: [HACKERS] Big IN() clauses etc : feature proposal |
| Previous Message | Tom Lane | 2006-05-10 15:10:37 | Re: UNSUBSCRIBE |