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

Re: SHMMAX seems entirely broken in OS X 10.4.2

From: Dave Cramer <pg(at)fastcrypt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jeff - <threshar(at)torgo(dot)978(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: SHMMAX seems entirely broken in OS X 10.4.2
Date: 2005-08-30 11:26:36
Message-ID: 2B7DD8A0-6109-4AC6-A90A-3BD7388E9453@fastcrypt.com (view raw or flat)
Thread:
Lists: pgsql-hackers
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(at)torgo(dot)978(dot)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
>
>


In response to

pgsql-hackers by date

Next:From: Hannu KrosingDate: 2005-08-30 11:27:42
Subject: Re: dangling lock information?
Previous:From: Mario WeilguniDate: 2005-08-30 10:51:44
Subject: Re: VACUUM/t_ctid bug (was Re: GiST concurrency commited)

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