| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Thomas Finneid <tfinneid(at)fcon(dot)no> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: explanation of some configs |
| Date: | 2009-02-07 00:59:11 |
| Message-ID: | 1233968351.15061.88.camel@jd-laptop.pragmaticzealot.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Sat, 2009-02-07 at 01:52 +0100, Thomas Finneid wrote:
> Hi
>
> I am having some problem understanding the details of a couple of
> configuration directives. Here is what I think I understand it so far:
>
> effective_cache_size
> - specifies in how many B/KB/MB will be used to cache data
> between pg and the OS?
> - what is actually cached and how it is actually used by the
> planner and how does it affect the planner and the queries?
> -in other words, when and why do I need to set this parameter?
This is just a hint to tell the planner how much cache will generally be
available. The number should be reflective of your shared buffers +
available operating system cache. If you database is postgresql only you
can generally set this very high 75% of available ram. If not then you
need to tone it down.
>
> checkpoint_segments
> - specifies the number of segments?
The number of segments that will be used before a checkpoint is forced.
> size: number*16MB?
Yes but they are not preallocated.
> - means when number of WAL segments has filled up and matches
> checkpoint segment, dirty data is written to disk?
A checkpoint occurs.
Joshua D. Drake
--
PostgreSQL - XMPP: jdrake(at)jabber(dot)postgresql(dot)org
Consulting, Development, Support, Training
503-667-4564 - http://www.commandprompt.com/
The PostgreSQL Company, serving since 1997
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Wong | 2009-02-07 05:31:46 | Re: Getting error while running DBT2 test for PostgreSQL |
| Previous Message | Thomas Finneid | 2009-02-07 00:52:17 | explanation of some configs |