| From: | Greg Smith <gsmith(at)gregsmith(dot)com> |
|---|---|
| To: | Justin <justin(at)emproshunts(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [PERFORM] Memory question on win32 systems |
| Date: | 2008-05-29 15:56:16 |
| Message-ID: | Pine.GSO.4.64.0805291150470.25714@westnet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 29 May 2008, Justin wrote:
> I'm confussed trying to figure out how caches are being use and being
> moving through postgresql backend.
The shared_buffers cache holds blocks from the database files. That's it.
If you want some more information about how that actually works head to
http://www.westnet.com/~gsmith/content/postgresql/ and read "Inside the
PostgreSQL Buffer Cache".
The work memory allocated for sorting is separate from that, and it
doesn't cache anything. It just provides working room for a query that's
being executed right now.
--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rick Vernam | 2008-05-29 15:58:19 | Re: Core team statement on replication in PostgreSQL |
| Previous Message | David Fetter | 2008-05-29 15:53:03 | Re: Core team statement on replication in PostgreSQL |