Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 3DEF69FA19B for ; Tue, 5 Dec 2006 19:07:17 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 61281-05 for ; Tue, 5 Dec 2006 19:07:09 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from mail.clickspace.com (torch1.clickspace.com [207.148.169.68]) by postgresql.org (Postfix) with ESMTP id A8C3C9F938C for ; Tue, 5 Dec 2006 19:07:12 -0400 (AST) Received: from localhost ([127.0.0.1]) by mail.clickspace.com (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)); Tue, 5 Dec 2006 16:06:43 -0700 Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Cc: Tom Lane , Guido Neitzer , Brendan Duddridge , "Jim C. Nasby" Content-Transfer-Encoding: 7bit From: Brian Wipf Subject: Re: shared_buffers > 284263 on OS X Date: Tue, 5 Dec 2006 16:06:41 -0700 To: pgsql-performance@postgresql.org X-Mailer: Apple Mail (2.752.2) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200612/97 X-Sequence-Number: 22153 I wanted to post a follow up to the list regarding a high shared_buffers value on OS X 10.4.8. Thanks to Tom's help we successfully compiled PostgreSQL 8.1.5 using 64-bit on OS X Server 10.4.8 (You can find info. for this on pgports) shared_buffers can now be set as high as shmmax without getting the error message "could not create shared memory segment...". Now, however, when shared_buffers are set greater than 279212 a segmentation fault occurs on startup of PostgreSQL. While trying to quantify the performance difference with higher shared_buffers versus relying more on the kernel cache, the difference does not appear as significant as I thought. We currently have shared_buffers set to about 25% of system memory on our box where we are free to set it within the bounds of shmmax (not OS X, of course). Brian Wipf