From: Greg Smith <greg@2ndQuadrant.com>
To: Leonardo Francalanci <m_lists@yahoo.it>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Adding more memory = hugh cpu load
Date: Tue, 11 Oct 2011 11:32:48 -0400
Message-ID: <4E9461A0.3070008@2ndQuadrant.com> (raw)
In-Reply-To: <1318323477.19815.YahooMailNeo@web29005.mail.ird.yahoo.com>
References: <4E92F294.9010405@gmail.com>
<4E92FB87.1030703@peak6.com>
<1318259675.10344.YahooMailNeo@web29011.mail.ird.yahoo.com>
<4E93119C.8090407@peak6.com>
<1318263277.56967.YahooMailNeo@web29013.mail.ird.yahoo.com>
<4E93E746.10807@2ndQuadrant.com>
<1318323477.19815.YahooMailNeo@web29005.mail.ird.yahoo.com>
On 10/11/2011 04:57 AM, Leonardo Francalanci wrote:
> In fact, shouldn't those things be explained in the "WAL
> Configuration" section
> of the manual? It looks as important as configuring Postgresql itself...
> And: that applies to Linux. What about other OS, such as Solaris and FreeBSD?
>
There's at least 10 pages of stuff about this floating around my book,
including notes on the similar Solaris and FreeBSD parameters to tune.
As for why that's not in the manual instead, two reasons. The
PostgreSQL manual doesn't get too deep into things like operating system
adjustments for performance. It's big enough without that, and any
information that would be added is likely to get out of sync with new OS
releases. This project doesn't want to take on the job of documenting
every twist there. My book is less than a year old, and there's already
some material on this topic that's turning obsolete due to Linux kernel
changes. The PostgreSQL manual is shooting to still be relevant for
much longer than that.
Second, making an addition to the manual is the hardest possible way to
document things. The docbook toolchain used is picky and fragile to
malformed additions. And you can't get anything added there without
passing through a series of people who will offer feedback of some sort;
usually valuable, but still time consuming to process. Things need to
asked quite frequently before it's worth the trouble. I did a few blog
entries and mailing list posts about this earlier this year, and that
was as much documentation as I could justify at the time. If there's a
user-visible behavior changes here, that's the point where an update to
the manual would be in order.
--
Greg Smith 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: greg@2ndQuadrant.com, m_lists@yahoo.it
Subject: Re: Adding more memory = hugh cpu load
In-Reply-To: <4E9461A0.3070008@2ndQuadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox