X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id A2E903A5578 for ; Tue, 25 Jan 2005 16:19:16 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 81517-01 for ; Tue, 25 Jan 2005 16:19:03 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 055C03A5792 for ; Tue, 25 Jan 2005 16:18:08 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j0PGI5dt003963; Tue, 25 Jan 2005 11:18:05 -0500 (EST) To: Don Drake Cc: pgsql-performance@postgresql.org Subject: Re: Postgres stopped running (shmget failed) In-reply-to: <6c21003b05012507104989efed@mail.gmail.com> References: <6c21003b05012507104989efed@mail.gmail.com> Comments: In-reply-to Don Drake message dated "Tue, 25 Jan 2005 09:10:50 -0600" Date: Tue, 25 Jan 2005 11:18:05 -0500 Message-ID: <3962.1106669885@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.007 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200501/466 X-Sequence-Number: 10156 Don Drake writes: > This morning I found the postgres not running and the following in my log file: > 2005-01-25 01:38:22 FATAL: could not create shared memory segment: > Cannot allocate memory > DETAIL: Failed system call was shmget(key=5432001, size=273383424, 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 273383424 bytes), reduce PostgreSQL's > shared_buffers parameter (currently 32768) and/or its max_connections > parameter (currently 40). I have seen this happen when the old shmem segment didn't get released for some reason, and your kernel settings are such that it won't allow creation of two shmem segments of that size at once. For robustness it's probably a good idea to make sure you *can* create two such segments at once, but for the moment getting rid of the old one with "ipcrm" should be enough to let you restart the postmaster. regards, tom lane