Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id E8B599FB85B for ; Thu, 21 Jun 2007 22:38:28 -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 29225-06 for ; Thu, 21 Jun 2007 22:38:17 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from alias11.ihug.co.nz (alias11.ihug.co.nz [203.96.222.21]) by postgresql.org (Postfix) with ESMTP id 29E1E9FB823 for ; Thu, 21 Jun 2007 22:38:24 -0300 (ADT) Received: from ironport2.ihug.co.nz [203.109.254.20] by alias11.ihug.co.nz with esmtp (Exim 3.36 #1 (Debian)) id 1I1Y6Q-0001gG-00; Fri, 22 Jun 2007 13:38:22 +1200 Received: from grunt5.ihug.co.nz (HELO ihug.co.nz) ([203.109.254.45]) by ironport2.ihug.co.nz with SMTP; 22 Jun 2007 13:38:23 +1200 X-Ironport-Seen: Yes From: Joe Barwell Reply-to: Joe Barwell To: Subject: Re: initdb problem X-Mailer: Quality Web Email v3.1m, http://netwinsite.com/refw.htm X-Originating-IP: 222.154.165.88 Date: Fri, 22 Jun 2007 13:38:22 +1200 Message-id: <467b280e.26e.6f03.423851873@ihug.co.nz> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.306 tagged_above=0 required=5 tests=AWL=0.105, BAYES_50=0.001, DNS_FROM_RFC_ABUSE=0.2 X-Spam-Level: X-Archive-Number: 200706/230 X-Sequence-Number: 25898 Tom Lane wrote: > Ugh. I don't recall exactly when Apple got around to > including ipcs, but I guess it wasn't in 10.3.9. Your > problem is that you're flying blind because you cannot > tell what's going on in shared memory. > > What I suspect is that there's an unused shared memory > segment sitting there (perhaps left over from a failed > initdb) and eating a sufficiently large fraction of SHMALL > that there's no room for another. If correct, then > rebooting should make it go away and let you initdb. Hi Tom, I get the same result trying to initdb after rebooting, the end of which is: fixing permissions on existing directory /Library/PostgreSQL8/data ... ok creating subdirectories ... ok selecting default max_connections ... 10 selecting default shared_buffers/max_fsm_pages ... 400kB/20000 creating configuration files ... ok creating template1 database in /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. To reduce the request size (currently 1646592 bytes), reduce PostgreSQL's shared_buffers parameter (currently 50) and/or its max_connections parameter (currently 10). The PostgreSQL documentation contains more information about shared memory configuration. child process exited with exit code 1 initdb: removing contents of data directory "/Library/PostgreSQL8/data" ---- Does the size=1646592 bit mean it's ignoring my /etc/sysctl.conf file? > Since you haven't got ipcrm either, there's basically no > other way to get rid of an unwanted shmem segment :-( > > You should think about upgrading to 10.4.x btw --- for > Postgres admin purposes, having ipcs and ipcrm available > is alone worth the price of admission. And it does seem > they've improved the OS's performance in various ways too. Out of my hands, it's not my computer to upgrade. Not even sure if a g4 will run 10.4.x, will it? Cheers! Joe