Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id EB4429FB58D for ; Tue, 3 Jul 2007 23:51:50 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 31363-05 for ; Tue, 3 Jul 2007 23:51:41 -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 8F0409FB5BB for ; Tue, 3 Jul 2007 23:51:47 -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 l642pjca017446; Tue, 3 Jul 2007 22:51:45 -0400 (EDT) To: Alvaro Herrera cc: ngaleyev@wavelengthmail.com, pgsql-admin@postgresql.org Subject: Re: hot restart of posgtresql In-reply-to: <20070704022944.GD6171@alvh.no-ip.org> References: <1210.209.168.137.101.1183505726.squirrel@wavelengthmail.com> <16558.1183514240@sss.pgh.pa.us> <20070704022944.GD6171@alvh.no-ip.org> Comments: In-reply-to Alvaro Herrera message dated "Tue, 03 Jul 2007 22:29:44 -0400" Date: Tue, 03 Jul 2007 22:51:45 -0400 Message-ID: <17445.1183517505@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200707/28 X-Sequence-Number: 26009 Alvaro Herrera writes: > Tom Lane wrote: >> ngaleyev@wavelengthmail.com writes: >>> 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? > Hmm, isn't shmall measured in pages? Depends on platform, which he didn't say ... but if it is a platform that measures in pages, I wonder whether that value is provoking an integer overflow somewhere. I don't think Linux allows more than about 2 million, for instance. > I think the problem may be that he changed the settings in sysctl.conf > but he hasn't rebooted since, so the kernel is running with other > settings. Trying with sysctl -w to change the actual values might prove > helpful. But his DB *was* running before, so somehow the active sysctl settings are different now than they were. I was betting on there having been a manual tweak to sysctl that never got made in the configuration file, and thus got lost on reboot. regards, tom lane