Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id D81F59FB992 for ; Thu, 21 Jun 2007 23:11:42 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 71907-07 for ; Thu, 21 Jun 2007 23:11:39 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from lists.commandprompt.com (host-254.commandprompt.net [207.173.203.254]) by postgresql.org (Postfix) with ESMTP id 7C9B19FB4DB for ; Thu, 21 Jun 2007 23:11:39 -0300 (ADT) Received: from [192.168.1.50] (or-67-76-146-141.sta.embarqhsd.net [67.76.146.141]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id l5M2Bcce031873; Thu, 21 Jun 2007 19:11:38 -0700 Message-ID: <467B3020.2020702@commandprompt.com> Date: Thu, 21 Jun 2007 19:12:48 -0700 From: "Joshua D. Drake" User-Agent: Thunderbird 1.5.0.12 (X11/20070604) MIME-Version: 1.0 To: Tom Lane CC: Joe Barwell , pgsql-admin@postgresql.org Subject: Re: initdb problem References: <467b280e.26e.6f03.423851873@ihug.co.nz> <10580.1182478082@sss.pgh.pa.us> In-Reply-To: <10580.1182478082@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.88.5, clamav-milter version 0.88.5 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Thu, 21 Jun 2007 19:11:39 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200706/232 X-Sequence-Number: 25900 Tom Lane wrote: > Joe Barwell writes: >> I get the same result trying to initdb after rebooting, the >> end of which is: >> /Library/PostgreSQL8/data/base/1 ... FATAL: could not >> create shared memory segment: Cannot allocate memory >> DETAIL: Failed system call was shmget(key=2, size=1646592, >> 03600). >> HINT: This error usually means that PostgreSQL's request >> for a shared memory segment exceeded available memory or >> swap space. > > Hmph. That is definitely not a SHMMAX violation (you get "Invalid > argument" for that). AFAIK the only two causes are SHMALL violation > (which, since your SHMMAX and SHMALL are effectively the same, means > someone is already eating part of SHMALL); or that you actually have not > got enough RAM to allocate the shmem segment. Which does not seem real > probable, for a mere 1.6MB. So I'm thinking something somewhere is > allocating a shmem segment behind your back. Maybe those earlier > "failed" attempts actually did install a working Postgres server? > You should troll through the "ps" listing carefully. Doesn't MacOSX install postgresql by default for one of their management services? Joshua D. Drake -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate PostgreSQL Replication: http://www.commandprompt.com/products/