X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 01E4BD1E935 for ; Tue, 13 Apr 2004 16:55:26 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 73329-04 for ; Tue, 13 Apr 2004 16:55:16 -0300 (ADT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 2D9C5D1C9BE for ; Tue, 13 Apr 2004 16:55:14 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i3DJtFjF025966; Tue, 13 Apr 2004 15:55:15 -0400 (EDT) To: Qing Zhao Cc: "'Postgresql Performance'" Subject: Re: configure shmmax on MAC OS X In-reply-to: <53A6FF52-8D7B-11D8-92CF-000A95AB8896@quotefx.net> References: <000801c42165$68a67750$4f01a8c0@jeremydunn> <24670.1081878949@sss.pgh.pa.us> <53A6FF52-8D7B-11D8-92CF-000A95AB8896@quotefx.net> Comments: In-reply-to Qing Zhao message dated "Tue, 13 Apr 2004 11:49:43 -0700" Date: Tue, 13 Apr 2004 15:55:15 -0400 Message-ID: <25965.1081886115@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/156 X-Sequence-Number: 6456 Qing Zhao writes: > My suspision is that the change i made in /etc/rc does not take > effect.Is there a way to check it? sysctl has an option to show the values currently in effect. I believe that /etc/rc is the correct place to set shmmax on OSX 10.3 or later ... but we have seen prior reports of people having trouble getting the setting to "take". There may be some other constraint involved. > sysctl -w kern.sysv.shmmax=4294967296 // byte Hmm, does sysctl work for values that exceed the range of int? There's no particularly good reason to try to set shmmax as high as you are trying anyhow; you really don't need more than a couple hundred meg in Postgres shared memory. It's better to leave the kernel to manage the bulk of your RAM. regards, tom lane