Received: from maia.hub.org (maia-4.hub.org [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 705A4633BC7 for ; Fri, 30 Apr 2010 12:57:59 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 53163-07 for ; Fri, 30 Apr 2010 15:57:52 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 1DA73633B21 for ; Fri, 30 Apr 2010 12:57:52 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id o3UFvjKq025929; Fri, 30 Apr 2010 11:57:46 -0400 (EDT) To: Gavin Kistner cc: pgsql-admin@postgresql.org Subject: Re: Fresh build on OS X not working (memory) In-reply-to: References: <88181C2E-01CD-417C-8266-D5C9AF570C27@mac.com> <15253.1272606140@sss.pgh.pa.us> Comments: In-reply-to Gavin Kistner message dated "Thu, 29 Apr 2010 23:58:54 -0600" Date: Fri, 30 Apr 2010 11:57:45 -0400 Message-ID: <25928.1272643065@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201004/368 X-Sequence-Number: 34462 Gavin Kistner writes: > On Apr 29, 2010, at 11:42 PM, Tom Lane wrote: >> For comparison, I have these settings on my laptop: >> pro:~ tgl$ cat /etc/sysctl.conf >> kern.sysv.shmmax=33554432 >> kern.sysv.shmmin=1 >> kern.sysv.shmmni=32 >> kern.sysv.shmseg=8 >> kern.sysv.shmall=8192 >> >> and PG starts fine for me. > I'm not sure what magic you have in there, but this incantation copied verbatim worked for me. Thanks! > The first sysctl.conf I tried that didn't work from from the one-click installer's README. Do you see anything about the following settings that jumps out at you as bad? Is it notable that yours don't set the maxproc*? > kern.sysv.shmmax=1610612736 > kern.sysv.shmall=393216 > kern.sysv.shmmin=1 > kern.sysv.shmmni=32 > kern.sysv.shmseg=8 > kern.maxprocperuid=512 > kern.maxproc=2048 I have no idea why EDB recommend changing the maxproc settings, but I doubt that's related to shared memory. I see that they have shmmax equal to exactly 4096 times shmall, so that's good, but there must be some other OSX peculiarity that this is tripping over. Maybe it's too large ... do you actually have 1.6GB of RAM available that could reasonably be dedicated to PG shared memory? Another possibility is that maybe only exact powers of 2 work well. I'm just guessing though. regards, tom lane