Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 731739FB7F4 for ; Wed, 23 May 2007 13:22:39 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 21389-01-3 for ; Wed, 23 May 2007 13:22:24 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.242]) by postgresql.org (Postfix) with ESMTP id C590C9FB741 for ; Wed, 23 May 2007 13:22:24 -0300 (ADT) Received: by an-out-0708.google.com with SMTP id c36so63300ana for ; Wed, 23 May 2007 09:22:22 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=WOmNRC5zjkIBOrixSgsxgW3dDKxZrpYKlzZY2eceeJ5cy00Z6N2UwjA/dIP7wlDwELtlFZ4XHp/f/5j54sel8vUGSyk916QkauRs+Bry/UhbLmoEU3mgO7UN331LVv5F4Sz6XHqYUgu5gkHg0B9puMStlbv9d3CnH2wzinDX5oc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=teRR0tlqyAZvGweGBaQkMdPw+JmlIXA7nGbbQnisjZKeA9hdiEqPo2lxWKDE4AWUEvk1thRHyGxIxEAnIFEBRqyXv0rpCAYg8Ls63TspfTvpiERo14SN+GgwPMLxx7CwKPdGbWwRDAuwJwdhaHDK9smfrGssJyW5t/U+ZNKqVD0= Received: by 10.100.37.4 with SMTP id k4mr640517ank.1179937342595; Wed, 23 May 2007 09:22:22 -0700 (PDT) Received: by 10.100.143.13 with HTTP; Wed, 23 May 2007 09:22:22 -0700 (PDT) Message-ID: Date: Wed, 23 May 2007 09:22:22 -0700 From: "Y Sidhu" To: pgsql-performance@postgresql.org Subject: max_fsm_pages, shared_buffers and checkpoint_segments MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_57931_11098374.1179937342446" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/459 X-Sequence-Number: 24849 ------=_Part_57931_11098374.1179937342446 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline I am a newbie, as you all know, but I am still embarassed asking this question. I started my tuning career by changing shared_buffers. Soon I discovered that I was hitting up against the available RAM on the system. So, I brought the number down. Then I discovered max_fsm_pages. I could take that up quite high and found out that it is a 'disk' thing. Then I started increasing checkpoint_segments,which is also a disk thing. However, setting it to 25, and then increasing any of the other 2 variables, the postgresql daemon stops working. meaning it does not start upon reboot. When I bring shared_buffers or max_fsm_pages back down, the daemon starts and all is normal. This happens on a 1 GB RAM machine and a 4 GB RAM machine. Anyone know what I am doing wrong? System: FreeBSD 6.1, Postgresql 8.09, 2 GB RAM -- Yudhvir Singh Sidhu 408 375 3134 cell ------=_Part_57931_11098374.1179937342446 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline I am a newbie, as you all know, but I am still embarassed asking this question. I started my tuning career by changing shared_buffers. Soon I discovered that I was hitting up against the available RAM on the system. So, I brought the number down. Then I discovered max_fsm_pages. I could take that up quite high and found out that it is a 'disk' thing. Then I started increasing checkpoint_segments,which is also a disk thing. However, setting it to 25, and then increasing any of the other 2 variables, the postgresql daemon stops working. meaning it does not start upon reboot. When I bring shared_buffers or max_fsm_pages back down, the daemon starts and all is normal. This happens on a 1 GB RAM machine and a 4 GB RAM machine.

Anyone know what I am doing wrong?

System:  FreeBSD 6.1, Postgresql 8.09, 2 GB RAM

--
Yudhvir Singh Sidhu
408 375 3134 cell ------=_Part_57931_11098374.1179937342446--