Received: from localhost (unknown [200.46.204.183])
	by mail.postgresql.org (Postfix) with ESMTP id 6E9FF64FD6F
	for <pgsql-docs-postgresql.org@mail.postgresql.org>;
	Mon, 15 Dec 2008 19:46:05 -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 78723-04 for
	<pgsql-docs-postgresql.org@mail.postgresql.org>;
	Mon, 15 Dec 2008 19:46:02 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from momjian.us (momjian.us [70.90.9.53])
	by mail.postgresql.org (Postfix) with ESMTP id 81EBA64FD6D
	for <pgsql-docs@postgresql.org>; Mon, 15 Dec 2008 19:46:02 -0400 (AST)
Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id
 mBFNk0W28273;
	Mon, 15 Dec 2008 18:46:00 -0500 (EST)
From: Bruce Momjian <bruce@momjian.us>
Message-Id: <200812152346.mBFNk0W28273@momjian.us>
Subject: Re: [ADMIN] shared_buffers and shmmax
In-Reply-To: <20081215234337.GP4067@alvh.no-ip.org>
To: Alvaro Herrera <alvherre@commandprompt.com>
Date: Mon, 15 Dec 2008 18:46:00 -0500 (EST)
CC: Tom Lane <tgl@sss.pgh.pa.us>, valiouk@yahoo.co.uk,
	pgsql-docs@postgresql.org, dx k9 <bitsandbytes88@hotmail.com>
X-Mailer: ELM [version 2.4ME+ PL124 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
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/8
X-Sequence-Number: 5015

Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > Tom Lane wrote:
> > > [ redirecting to pgsql-docs ]
> > > 
> > > Valentin Bogdanov <valiouk@yahoo.co.uk> writes:
> > > >> From: dx k9 <bitsandbytes88@hotmail.com>
> > > >> 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.

Well, the heading says "object" now so I thought it would suggest we are
talking about objects and not bytes.

> > ***************
> > *** 1119,1125 ****
> >   
> >         <row>
> >          <entry>Fixed space requirements</>
> > !        <entry>770 kB</entry>
> >         </row>
> >        </tbody>
> >       </tgroup>
> > --- 1119,1125 ----
> >   
> >         <row>
> >          <entry>Fixed space requirements</>
> > !        <entry>770 k</entry>
> >         </row>
> >        </tbody>
> >       </tgroup>
> 
> This change is wrong, why did you do it?

The heading says "bytes" so having the "B" was unnecessary and possibly
confusing.


-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +