X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 9916CD1B194 for ; Fri, 21 May 2004 13:59:21 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 35491-10 for ; Fri, 21 May 2004 13:59:01 -0300 (ADT) Received: from netcetrallc.com (unknown [209.196.42.213]) by svr1.postgresql.org (Postfix) with ESMTP id 90449D1B1C7 for ; Fri, 21 May 2004 13:59:00 -0300 (ADT) Received: from WORKSTATION (c-24-1-91-108.client.comcast.net [24.1.91.108]) by netcetrallc.com (8.12.9/8.12.9) with SMTP id i4LFuDWG009220 for ; Fri, 21 May 2004 11:56:13 -0400 Message-ID: <406e01c43f55$32d6bb40$0200a8c0@WORKSTATION> From: "Kevin Schroeder" To: References: <20040521155715.E15B0430E@jimsun.LinxNet.com> Subject: Re: Shared memory error using initdb on Solaris 8 Date: Fri, 21 May 2004 12:01:02 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.2 tagged_above=0.0 required=5.0 tests=RCVD_IN_RFCI, RCVD_IN_SORBS X-Spam-Level: X-Archive-Number: 200405/230 X-Sequence-Number: 13546 There we go. For reference, what page did you get that info and what did you search for to get it? Kevin ----- Original Message ----- From: "Jim Seymour" To: Sent: Friday, May 21, 2004 10:57 AM Subject: Re: [ADMIN] Shared memory error using initdb on Solaris 8 > > > > Hello, > > I'm trying to install PostgreSQL 7.4.2 on a brand new SunFire 120 with > > 2GB of RAM but when I run initdb -D /usr/local/pgsql/data I get the > > following error: > > > [snip] > > creating template1 database in /usr/local/pgsql/data/base/1... FATAL: could > > not create shared memory segment: Invalid argument > > DETAIL: Failed system call was shmget(key=1, size=1081344, 03600). > > HINT: This error usually means that PostgreSQL's request for a shared > > memory segment exceeded your kernel's SHMMAX parameter. > [snip] > > > > When I run ulimit -a I get > > > [snip] > > You're looking at the wrong thing. You need to do: > > sysdef |egrep -i 'shm|sem' > > > > > There does not seem to be an option in initdb to reduce the shared buffers > > size. > > It tries to reduce things as far as it "sanely" can to fit within > what's available. You can hand-tweak initdb to over-ride its > limits, but you'd end-up with a sub-optimal installation. > > > Plus, with 2GB of RAM I don't know that I'd want to go below the > > "lowest common denominator" that Postgres defaults to. > > Nope. You need to adjust certain values by placing settings in > /etc/system and rebooting. I use: > > /etc/system > set shmsys:shminfo_shmmax=0x2000000 (33554432 decimal) > set shmsys:shminfo_shmmin=1 > set shmsys:shminfo_shmmni=256 > set shmsys:shminfo_shmseg=256 > > set semsys:seminfo_semmap=256 > set semsys:seminfo_semmni=512 > set semsys:seminfo_semmns=512 > set semsys:seminfo_semmsl=32 > > I arrived at the above values from Google'ing. > > Jim > > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faqs/FAQ.html