Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 07B38650308; Thu, 24 Jul 2008 15:02:53 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 26783-06; Thu, 24 Jul 2008 15:02:40 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by postgresql.org (Postfix) with ESMTP id 2FCB3650332; Thu, 24 Jul 2008 15:02:40 -0300 (ADT) Received: from [192.168.1.5] (or-69-34-217-90.sta.embarqhsd.net [69.34.217.90]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m6OI572l004349 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 24 Jul 2008 11:05:07 -0700 Subject: Re: [DOCS] [ADMIN] shared_buffers and shmmax From: "Joshua D. Drake" To: Greg Sabino Mullane Cc: pgsql-docs@postgresql.org, pgsql-hackers@postgresql.org In-Reply-To: <3bd4182ebf79bc4a171f08d03d2edb2f@biglumber.com> References: <3bd4182ebf79bc4a171f08d03d2edb2f@biglumber.com> Content-Type: text/plain Organization: Command Prompt, Inc. Date: Thu, 24 Jul 2008 11:02:39 -0700 Message-Id: <1216922559.6858.56.camel@jd-laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Thu, 24 Jul 2008 11:05:08 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200807/1142 X-Sequence-Number: 121402 On Thu, 2008-07-24 at 17:54 +0000, Greg Sabino Mullane wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: RIPEMD160 > NotDashEscaped: You need GnuPG to verify this message > > > >> shared_buffers is in disk block size, typically 8K > > > The table the OP is looking at (table 17.2 in the 8.3 docs) predates > > the ability to specify shared_buffers in KB or MB instead of > > number-of-buffers. I agree it's not entirely obvious that what it > > means is "multiply your setting in KB/MB by 8400/8192". Anybody have > > an idea how to clarify things? > > Bite the bullet and start showing the buffer settings as a pure number of bytes > everywhere, and get rid of the confusing '8kB' unit in pg_settings? +1 We have helper functions like pg_size_pretty() to resolve the other issues. Joshua D. Drake -- The PostgreSQL Company since 1997: http://www.commandprompt.com/ PostgreSQL Community Conference: http://www.postgresqlconference.org/ United States PostgreSQL Association: http://www.postgresql.us/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate