Skip site navigation (1) Skip section navigation (2)

Re: SHMMAX seems entirely broken in OS X 10.4.2

From: "Thomas F(dot) O'Connell" <tfo(at)sitening(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: SHMMAX seems entirely broken in OS X 10.4.2
Date: 2005-08-30 02:46:09
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
In order to get postgres working in concert with an iSight on a  
PowerBook, I had to increase shmmax, and it seemed to work just fine  
by editing /etc/rc:

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

After restarting, I have:

# sysctl -a | grep shm
kern.sysv.shmmax: 134217728
kern.sysv.shmmin: 1
kern.sysv.shmmni: 32
kern.sysv.shmseg: 8
kern.sysv.shmall: 1024

Of course, this still doesn't seem to be enough to let postgres play  
nicely with the iSight...

Thomas F. O'Connell
Co-Founder, Information Architect
Sitening, LLC

Strategic Open Source: Open Your i™
110 30th Avenue North, Suite 6
Nashville, TN 37203-6320
615-469-5151 (fax)

On Aug 29, 2005, at 7:18 PM, Tom Lane wrote:

> Has anyone been able to set kern.sysv.shmmax above 4MB at all in  
> latest
> OS X?  I just spent a while trying what seemed every possible
> permutation of setting up /etc/sysctl.conf and editing /etc/rc  
> directly,
> and it just fails (symptom: sysctl shows shmmax as -1, and Postgres
> cannot start).
> Grrr.  Apple's been pretty lame about this from day one, but at least
> it's been possible to do it one way or another.
> (Curiously, it seems you can now change shmall after bootup in 10.4.2,
> but that's not much help when you can't change shmmax.)
>             regards, tom lane

In response to


pgsql-hackers by date

Next:From: Luke LonerganDate: 2005-08-30 03:13:20
Subject: Re: SHMMAX seems entirely broken in OS X 10.4.2
Previous:From: Allan WangDate: 2005-08-30 02:35:18
Subject: Re: Work-in-progress referential action trigger timing patch

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group