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 5C5B0D1E96B for ; Tue, 13 Apr 2004 17:59:28 -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 99637-08 for ; Tue, 13 Apr 2004 17:59:27 -0300 (ADT) Received: from hosting.commandprompt.com (128.commandprompt.com [207.173.200.128]) by svr1.postgresql.org (Postfix) with ESMTP id 62A72D1E98F for ; Tue, 13 Apr 2004 17:59:24 -0300 (ADT) Received: from commandprompt.com (dsl093-038-087.pdx1.dsl.speakeasy.net [66.93.38.87]) (authenticated) by hosting.commandprompt.com (8.11.6/8.11.6) with ESMTP id i3DKxIP32349; Tue, 13 Apr 2004 13:59:18 -0700 Message-ID: <407C54A1.6090908@commandprompt.com> Date: Tue, 13 Apr 2004 13:59:13 -0700 From: "Joshua D. Drake" Organization: Command Prompt, Inc. User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane Cc: Qing Zhao , "'Postgresql Performance'" Subject: Re: configure shmmax on MAC OS X References: <000801c42165$68a67750$4f01a8c0@jeremydunn> <24670.1081878949@sss.pgh.pa.us> <53A6FF52-8D7B-11D8-92CF-000A95AB8896@quotefx.net> <25965.1081886115@sss.pgh.pa.us> In-Reply-To: <25965.1081886115@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/159 X-Sequence-Number: 6459 Hello, I found that if you SHMALL value was less than your SHMMAX value, the value wouldn't take. J Tom Lane wrote: > 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 > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Don't 'kill -9' the postmaster