Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 07CF764FD6D for ; Mon, 15 Dec 2008 19:43:58 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 78242-03 for ; Mon, 15 Dec 2008 19:43:55 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by mail.postgresql.org (Postfix) with ESMTP id 0CE1E64FCBE for ; Mon, 15 Dec 2008 19:43:54 -0400 (AST) Received: from perhan.alvh.no-ip.org (200-126-65-108.bk5-dsl.surnet.cl [200.126.65.108]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id mBFNmiRN028722 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Dec 2008 15:48:47 -0800 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 7371647CCD; Mon, 15 Dec 2008 20:43:37 -0300 (CLST) Date: Mon, 15 Dec 2008 20:43:37 -0300 From: Alvaro Herrera To: Bruce Momjian Cc: Tom Lane , valiouk@yahoo.co.uk, pgsql-docs@postgresql.org, dx k9 Subject: Re: [ADMIN] shared_buffers and shmmax Message-ID: <20081215234337.GP4067@alvh.no-ip.org> References: <28167.1216737959@sss.pgh.pa.us> <200812152323.mBFNN3Y25121@momjian.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200812152323.mBFNN3Y25121@momjian.us> User-Agent: Mutt/1.5.18 (2008-05-17) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Mon, 15 Dec 2008 15:48:48 -0800 (PST) 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: 200812/7 X-Sequence-Number: 5014 Bruce Momjian wrote: > Tom Lane wrote: > > [ redirecting to pgsql-docs ] > > > > Valentin Bogdanov writes: > > >> From: dx k9 > > >> I'm trying to understand what the documentation means > > >> by bytes per increment, what is the increment supposed to > > >> be bytes, MB, or Kb. > > > > > shared_buffers is in disk block size, typically 8K, at least that's what it is on Linux platforms. shmmax is quite simply in bytes. > > > > 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? > > I have updated the table title to be clearer. I don't find it any clearer ... I think the missing clue is that if you specify shared_buffers values in MB, you must divide the value by block size. > *************** > *** 1119,1125 **** > > > Fixed space requirements > ! 770 kB > > > > --- 1119,1125 ---- > > > Fixed space requirements > ! 770 k > > > This change is wrong, why did you do it? -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support