Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229])
	by mail.postgresql.org (Postfix) with ESMTP id 978CD7661B5
	for <pgsql-admin@postgresql.org>; Thu, 21 Jun 2012 04:21:02 -0300 (ADT)
Received: from moutng.kundenserver.de ([212.227.126.186])
	by magus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <greg@2ndQuadrant.com>) id 1ShbhM-0003uT-7h
	for pgsql-admin@postgresql.org; Thu, 21 Jun 2012 07:21:01 +0000
Received: from [192.168.1.6] (mail.highperformancepostgresql.com
	[71.179.240.8])
	by mrelayeu.kundenserver.de (node=mreu2) with ESMTP (Nemesis)
	id 0LqHEi-1SCgnO2XGy-00e1kY; Thu, 21 Jun 2012 09:20:46 +0200
Message-ID: <4FE2CB4D.4000108@2ndQuadrant.com>
Date: Thu, 21 Jun 2012 03:20:45 -0400
From: Greg Smith <greg@2ndQuadrant.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
	rv:1.9.2.24) Gecko/20111120 Icedove/3.1.16
MIME-Version: 1.0
To: pgsql-admin@postgresql.org
Subject: Re: about shared_buffer and kernel.shmmax
References: <4FE29737.2040405@edgesoft.cn>
In-Reply-To: <4FE29737.2040405@edgesoft.cn>
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 7bit
X-Provags-ID: V02:K0:1/HMRmG5ehivX/0784EDp/LMM0uo6NsqybyxenrAS/X
	GDsbNzX0Xa33ApaoT5ZeoLZX9+JRbTlWucbsB9z5bbvzRFXTGO
	mPebGmC3sPjzSk1DLnMEDpcWYSkFDKl4A3jylPZnidP0umDHjT
	F+MH6F/POlvILhqEepVgmQ3ydXUVGgIIxsUUWd6nHtmviI/+Ug
	I4RCpMHmFg4Mp9t7fiOC7OXhW2LM+v4ioNX8Tbpp60sHTwtu/T
	ihAt4VK5XG9ilmbba0kHIUDOFPumJn9JhkhQwqAM93m5oGrL1H
	FH3sbn7TrmglhP6cIakvfXmpg1+rA0UkX0UIqsuY6wgPMploU9
	WyjuO1bx1qwtfrqs3nac=
X-Pg-Spam-Score: -1.9 (-)
X-Archive-Number: 201206/97
X-Sequence-Number: 39688

On 06/20/2012 11:38 PM, wangqi wrote:
> shared_buffer maximum limit is ?
> I set shared_buffer more than 250G, I got error at startup pg.

There's not much evidence that values larger than 16GB are really
productive.  You really do not want put all their memory in just that
one place.

-- 
Greg Smith   2ndQuadrant US    greg@2ndQuadrant.com   Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.com