Date: Wed, 22 May 2002 13:02:51 -0400
From: Gregory Seidman <gss+pg@cs.brown.edu>
To: pgsql-general@postgresql.org
Subject: Re: MacOS X Shared Buffers (SHMMAX)?
Message-ID: <20020522130251.B7586@jamaica.cs.brown.edu>
Reply-To: gss+pg@cs.brown.edu
References: <B90F1435.D909%slane@fmpro.com>
	<Pine.LNX.4.30.0205220939590.14696-100000@commandprompt.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <Pine.LNX.4.30.0205220939590.14696-100000@commandprompt.com>;
	from pgsql-general@commandprompt.com on Wed, May 22, 2002 at
	10:30:00AM -0700

Command Prompt, Inc. sez:
[...]
} [...actually, a minute later of looking at the source...]
} 
} Okay, so it appears to be when it's checking sockets for data in
} src/backend/postmaster/pgstat.c, line 1579...I just tried re-building the
} kernel with a higher value for kern.ipc.maxsockets but that didn't have
} any effect, still get that error.
} 
} Anyone have any ideas on what specifically would cause this part of pgstat
} to fail?

Recompiling the kernel was necessary to change the shared memory limit, but
kern.ipc.maxsockets can be changed on the fly with sysctl. It might be
getting changed in one of the scripts (perhaps SystemTuning) in
/System/Library/StartupItems (there are also sometimes scripts in
/Library/StartupItems; both directories are used in the startup process).
When your system is up and running, try sysctl kern.ipc.maxsockets and see
if the value is what you expected. If not, dig around in the StartupItems
directories and see if something is changing it.

} Best regards,
} Jw.
--Greg