Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 17C17632B51 for ; Fri, 30 Apr 2010 02:42:32 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 99701-06 for ; Fri, 30 Apr 2010 05:42:22 +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 492E4632B09 for ; Fri, 30 Apr 2010 02:42:22 -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 o3U5gKAW015254; Fri, 30 Apr 2010 01:42:20 -0400 (EDT) To: Gavin Kistner cc: pgsql-admin@postgresql.org Subject: Re: Fresh build on OS X not working (memory) In-reply-to: <88181C2E-01CD-417C-8266-D5C9AF570C27@mac.com> References: <88181C2E-01CD-417C-8266-D5C9AF570C27@mac.com> Comments: In-reply-to Gavin Kistner message dated "Thu, 29 Apr 2010 23:32:10 -0600" Date: Fri, 30 Apr 2010 01:42:20 -0400 Message-ID: <15253.1272606140@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.892 tagged_above=-10 required=5 tests=AWL=0.018, BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201004/360 X-Sequence-Number: 34454 Gavin Kistner writes: > Mac OS X 10.6.3 > Built and installed PG 8.4.3 from source > Trying to start the server, I get "could not create shared memory segment: Invalid argument". OSX is *notoriously* unfriendly about configuring shm parameters. You look at it sidewise, it doesn't work, and generally won't tell you why it's refusing to talk to you. We document a few of the known constraints in our manual, but I'm sure there are more. > Slim2:pgsql _postgres$ sysctl -a | grep shm > kern.sysv.shmmax: 2147483648 > kern.sysv.shmmin: 1 > kern.sysv.shmmni: 32 > kern.sysv.shmseg: 8 > kern.sysv.shmall: 2147483648 Hm. That shmall setting is not sane at all (remember the units are pages). I wonder whether you've forced some internal overflow inside the kernel. 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. regards, tom lane