| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Scott Carey <scott(at)richrelevance(dot)com>, Christiaan Willemsen <cwillemsen(at)technocon(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Configuring for maximum memory usage |
| Date: | 2008-10-30 17:26:26 |
| Message-ID: | 1225387586.32621.24.camel@jd-laptop.pragmaticzealot.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Thu, 2008-10-30 at 14:00 -0300, Alvaro Herrera wrote:
> Joshua D. Drake wrote:
>
> > However that isn't the exact same thing as a "cache" at least as I was
> > trying to describe it. shared buffers are used to keep track of pages
> > (as well as some other stuff) and their current status. That is not the
> > same as caching a relation.
>
> Um, having a page in shared buffers means exactly that the page is
> cached (a.k.a. it won't have to be read from the lower level next time).
>
Yes but that wasn't my point. Sorry if I wasn't being clear enough.
Joshua D. Drake
--
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Carey | 2008-10-30 17:37:23 | Re: Configuring for maximum memory usage |
| Previous Message | Alvaro Herrera | 2008-10-30 17:00:23 | Re: Configuring for maximum memory usage |