Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 9D0869F927D for ; Sun, 28 Oct 2007 14:14:21 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 02979-05-2 for ; Sun, 28 Oct 2007 14:14:16 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 8AE129F9FE6 for ; Sun, 28 Oct 2007 14:14:16 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l9SHECQu000871; Sun, 28 Oct 2007 13:14:12 -0400 (EDT) To: Maximilian Tyrtania cc: pgsql-admin@postgresql.org Subject: Re: shared memory settings on MAC OS X In-reply-to: References: Comments: In-reply-to Maximilian Tyrtania message dated "Sun, 28 Oct 2007 16:02:18 +0100" Date: Sun, 28 Oct 2007 13:14:12 -0400 Message-ID: <870.1193591652@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/280 X-Sequence-Number: 27194 Maximilian Tyrtania writes: > I am trying to increase the amount of shared memory on my Mac OS 10.4 > machine (i have 5 GB RAM installed), but without too much success. Weird, those same exact settings work fine for me. How up-to-date is your 10.4.x installation? The relevant part of /etc/rc in mine is if [ -f /etc/sysctl-macosxserver.conf ]; then awk '{ if (!index($1, "#") && index($1, "=")) print $1 }' < /etc/sysctl\ -macosxserver.conf | while read do sysctl -w ${REPLY} done fi if [ -f /etc/sysctl.conf ]; then awk '{ if (!index($1, "#") && index($1, "=")) print $1 }' < /etc/sysctl\ .conf | while read do sysctl -w ${REPLY} done fi sysctl -w kern.sysv.shmmax=4194304 kern.sysv.shmmin=1 kern.sysv.shmmni=32 kern.\ sysv.shmseg=8 kern.sysv.shmall=1024 So one obvious gotcha would be if you have a /etc/sysctl-macosxserver.conf file that sets 'em differently. The gotchas I know about in this area are: * The OSX kernel seems to lock down the shmem settings as soon as all five have been correctly specified via sysctl. This is why the sysctl done last in /etc/rc doesn't overwrite yours. * It's fairly draconian about what "correctly specified" is --- notably, at least some versions insist on shmmax being an exact multiple of the page size. But the numbers you quoted look OK. regards, tom lane