| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Donald Courtney <Donald(dot)Courtney(at)Sun(dot)COM> |
| Cc: | pgsql-performance(at)postgresql(dot)org, Frank Wiles <frank(at)wiles(dot)org>, gokulnathbabu manoharan <gokulnathbabu(at)yahoo(dot)com> |
| Subject: | Re: Caching by Postgres |
| Date: | 2005-08-23 19:23:43 |
| Message-ID: | 4587.1124825023@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Donald Courtney <Donald(dot)Courtney(at)Sun(dot)COM> writes:
> I am not alone in having the *expectation* that a database should have
> some cache size parameter and the option to skip the file system. If
> I use oracle, sybase, mysql and maxdb they all have the ability to
> size a data cache and move to 64 bits.
And you're not alone in holding that opinion despite having no shred
of evidence that it's worthwhile expanding the cache that far.
However, since we've gotten tired of hearing this FUD over and over,
8.1 will have the ability to set shared_buffers as high as you want.
I expect next we'll be hearing from people complaining that they
set shared_buffers to use all of RAM and performance went into the
tank ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2005-08-23 19:38:04 | Re: Caching by Postgres |
| Previous Message | John Mendenhall | 2005-08-23 19:05:25 | Re: complex query performance assistance request |