From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Qing Zhao <qzhao(at)quotefx(dot)net>, "'Postgresql Performance'" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: configure shmmax on MAC OS X |
Date: | 2004-04-13 20:59:13 |
Message-ID: | 407C54A1.6090908@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
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 <qzhao(at)quotefx(dot)net> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-04-13 21:23:36 | Re: View columns calculated |
Previous Message | Peter Darley | 2004-04-13 20:49:53 | View columns calculated |