Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 726299FBEC6 for ; Wed, 4 Jul 2007 03:38:01 -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 52532-04 for ; Wed, 4 Jul 2007 03:37:56 -0300 (ADT) X-Greylist: delayed 07:02:57.360203 by SQLgrey-1.7.5 Received: from mail.wavelengthmail.com (mail.wavelengthmail.com [208.65.225.2]) by postgresql.org (Postfix) with ESMTP id CE1C69FBEA4 for ; Wed, 4 Jul 2007 03:37:57 -0300 (ADT) Received: from wavelengthmail.com (secure.gowavelength.com [208.65.225.4]) by mail.wavelengthmail.com (wavelengthmail.com) with ESMTP id 93BB82FBBF for ; Wed, 4 Jul 2007 02:37:52 -0400 (EDT) Received: from 209.168.137.101 (SquirrelMail authenticated user ngaleyev@wavelengthmail.com) by wavelengthmail.com with HTTP; Wed, 4 Jul 2007 02:38:23 -0400 (EDT) Message-ID: <1089.209.168.137.101.1183531103.squirrel@wavelengthmail.com> Date: Wed, 4 Jul 2007 02:38:23 -0400 (EDT) Subject: Re: hot restart of posgtresql From: ngaleyev@wavelengthmail.com To: pgsql-admin@postgresql.org User-Agent: SquirrelMail/1.5.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.097 tagged_above=0 required=5 tests=BAYES_50=0.001, FORGED_RCVD_HELO=0.135, NO_REAL_NAME=0.961 X-Spam-Level: * X-Archive-Number: 200707/30 X-Sequence-Number: 26011 thanks for replies everyone platform is Debian 2.6 btw Heres how i got temp fix (i dont have much background in postgresql, so dont kick me hard): few months ago old admin upgraded to 6GB of ram and increased shared_buffers in posgresql.conf from 16384 to 393216 (3GB) He also modifed sysctl to look like this: ----- kernel.shmmax=4294967296 kernel.shmall=536870912 ----- I looked in top command, and dmesg, both indicate 6GB of ram. So I started gradually increase "sysctl -w kernel.shmmax=xxx" during that i was checking out /proc/sys/kernel/shmmax it was keeping up with corresponding values until i reached that number - 4294967296, it was showing "0" instead. so i lowered it to 4200000000, about highest number that would not null that /proc value. Still wouldnt start :( but with different error now, didnt save it After that i decreased shared_buffers back to 16384, and it worked. Didnt mess with it anymore for right now, don't want to experiment on live server. Old admin is not around anymore, so I sort of inherited responsibility for the server, but I don't know much about postgresql yet. So, whats the optimum values for this amount of memory as far as SHMALL, MAX and shared_buffers? Database size is about 115GB, daily traffic is about 800MB. Thanks alot -Nik