Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 900509FBB74 for ; Tue, 3 Jul 2007 22:57:25 -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 24125-07 for ; Tue, 3 Jul 2007 22:57:22 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 6AB3D9FBB23 for ; Tue, 3 Jul 2007 22:57:22 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l641vKQ1016559; Tue, 3 Jul 2007 21:57:21 -0400 (EDT) To: ngaleyev@wavelengthmail.com cc: pgsql-admin@postgresql.org Subject: Re: hot restart of posgtresql In-reply-to: <1210.209.168.137.101.1183505726.squirrel@wavelengthmail.com> References: <1210.209.168.137.101.1183505726.squirrel@wavelengthmail.com> Comments: In-reply-to ngaleyev@wavelengthmail.com message dated "Tue, 03 Jul 2007 19:35:26 -0400" Date: Tue, 03 Jul 2007 21:57:20 -0400 Message-ID: <16558.1183514240@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200707/26 X-Sequence-Number: 26007 ngaleyev@wavelengthmail.com writes: > 2007-07-03 19:20:42 EDT 2928 FATAL: could not create shared memory > segment: Invalid argument > 2007-07-03 19:20:42 EDT 2928 DETAIL: Failed system call was > shmget(key=5432001, size=3276259328, 03600). > 2007-07-03 19:20:42 EDT 2928 HINT: This error usually means that > PostgreSQL's request for a shared memory segment exceeded your kernel's > SHMMAX parameter. You can either reduce the request size or reconfigure > the kernel with larger SHMMAX. To reduce the request size (currently > 3276259328 bytes), reduce PostgreSQL's shared_buffers parameter (currently > 393216) and/or its max_connections parameter (currently 250). > heres my sysctl: > kernel.shmmax=4294967296 > kernel.shmall=536870912 Why have you got SHMALL set to half a GB when you have Postgres configured to ask for over 3 GB? regards, tom lane