Tom,

On 8/29/05 9:37 PM, "Tom Lane" <tgl@sss.pgh.pa.us> wrote:

> Did that. Set shmall first, shmall second, both together in one sysctl
> command; no joy anywhere. Are you trying this on fully up-to-date
> Tiger?

Did you try the values I sent earlier? If you set them both in
/etc/sysctl.conf and reboot, it should work. We get 100% repeatability on
10.4.2 platforms.

- Luke



---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

This is from my Powerbook

in /etc/rc

sysctl -w kern.sysv.shmmax=5120000 kern.sysv.shmmin=1
kern.sysv.shmmni=32 kern.sysv.shmseg=8 kern.sysv.shmall=1024

I also had to up maxprocperuid to 200 to get buildfarm to run

I'm pretty sure shmall had to be increased to allow shmmax to be
increased.


Dave
On 30-Aug-05, at 12:37 AM, Tom Lane wrote:

> Jeff - <threshar@torgo.978.org> writes:
>
>> On Aug 29, 2005, at 8:18 PM, Tom Lane wrote:
>>
>>> Has anyone been able to set kern.sysv.shmmax above 4MB at all in
>>> latest OS X?
>>>
>
>
>> yeah, you need to set shmmax and shmall.
>>
>
> Did that. Set shmall first, shmall second, both together in one
> sysctl
> command; no joy anywhere. Are you trying this on fully up-to-date
> Tiger?
>
> regards, tom lane
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
>


---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

On Aug 30, 2005, at 12:37 AM, Tom Lane wrote:

>
> Did that. Set shmall first, shmall second, both together in one
> sysctl
> command; no joy anywhere. Are you trying this on fully up-to-date
> Tiger?
>

Just ran software update and (besides a couple apps) it had a
security update.

skittlebrau:~ postgres$ grep shm /etc/rc
# sysctl -w kern.sysv.shmmax=4194305 kern.sysv.shmmin=1
kern.sysv.shmmni=32 kern.sysv.shmseg=8 kern.sysv.shmall=1024
sysctl -w kern.sysv.shmmax=335544320
sysctl -w kern.sysv.shmmin=1
sysctl -w kern.sysv.shmmni=32
sysctl -w kern.sysv.shmseg=16
sysctl -w kern.sysv.shmall=327680

skittlebrau:~ postgres$ sysctl -a | grep shm
kern.sysv.shmmax: 335544320
kern.sysv.shmmin: 1
kern.sysv.shmmni: 32
kern.sysv.shmseg: 16
kern.sysv.shmall: 327680

good luck.

--
Jeff Trout <jeff@jefftrout.com>
http://www.jefftrout.com/
http://www.stuarthamm.net/



---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Jeff,

On 8/30/05 5:28 AM, "Jeff Trout" <threshar@torgo.978.org> wrote:

> Just ran software update and (besides a couple apps) it had a
> security update.

I just did that to test this.

> skittlebrau:~ postgres$ grep shm /etc/rc

Luke-Lonergans-Computer:~ lukelonergan$ cat /etc/sysctl.conf
kern.sysv.shmall=327680
kern.sysv.shmmax=335544320
#kern.sysv.shmall=268435456
#kern.sysv.shmmax=268435456

> skittlebrau:~ postgres$ sysctl -a | grep shm

Luke-Lonergans-Computer:~ lukelonergan$ sysctl -a | grep shm
kern.sysv.shmmax: 335544320
kern.sysv.shmmin: 1
kern.sysv.shmmni: 32
kern.sysv.shmseg: 8
kern.sysv.shmall: 327680

Thx for the tip.

I also tried different settings (shmall set to 500K) and shmmax ended up at
-1. So, it seems that shmall is in pages. I didn't try other allowable
configs, which was a problem before.

- Luke



---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

[ resuming an old thread ]

"Luke Lonergan" <llonergan@greenplum.com> writes:
> I also tried different settings (shmall set to 500K) and shmmax ended up at
> -1. So, it seems that shmall is in pages. I didn't try other allowable
> configs, which was a problem before.

I went back and experimented some more with this issue, and I believe
I've finally nailed down what the problem is: as of 10.4.something, OS X
rejects attempts to set SHMMAX to anything that isn't an exact multiple
of the page size (4096). Every other Unix on the planet, including
earlier versions of OS X, will round off the value to whatever unit
they feel like supporting ... but not Tiger. Thanks for this usability
improvement, Apple.

Also, the /etc/sysctl.conf file is utterly useless for setting SHM
settings in 10.4.2, because whatever it sets will be overridden by the
sysctl command that /etc/rc does just after reading /etc/sysctl.conf.
Perhaps in prior versions, the behavior was "first set wins" ... but
now it is definitely "last set wins". (SHMMAX eventually gets locked
down and can't be changed anymore; I'm not sure what triggers that,
but the sysctl in /etc/rc definitely gets to change what you put in
/etc/sysctl.conf.) Perhaps Apple can be persuaded to change the order
of these operations in /etc/rc, but until they do there is no point
in suggesting that people use /etc/sysctl.conf.

Bottom line: in 10.4.2, you have to edit /etc/rc to adjust SHMMAX,
and you'd better be sure it is an exact multiple of 4096.

I'll add a note about this to our documentation.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings