Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 42AFD9F9FE1 for ; Wed, 20 Dec 2006 04:59:45 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 24761-04 for ; Wed, 20 Dec 2006 04:59:34 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from mx3.ipf.is (man.ipf.is [85.197.192.163]) by postgresql.org (Postfix) with ESMTP id 38E0A9F9F46 for ; Wed, 20 Dec 2006 04:59:36 -0400 (AST) Received: (qmail 29444 invoked by uid 1010); 20 Dec 2006 08:52:34 +0000 Received: from 88.149.106.19 by man (envelope-from , uid 1008) with qmail-scanner-1.25-st-qms (clamdscan: 0.88.4/1639. spamassassin: 3.1.4. perlscan: 1.25-st-qms. Clear:RC:1(88.149.106.19):SA:0(-2.5/4.5):. Processed in 2.65237 secs); 20 Dec 2006 08:52:34 -0000 X-Antivirus-HIVE-Mail-From: gnari@hive.is via man X-Antivirus-HIVE: 1.25-st-qms (Clear:RC:1(88.149.106.19):SA:0(-2.5/4.5):. Processed in 2.65237 secs Process 29429) Received: from dsl-149-106-19.hive.is (HELO ?192.168.1.33?) (88.149.106.19) by mx3.ipf.is with SMTP; 20 Dec 2006 08:52:31 +0000 Subject: Re: max_fsm_pages and check_points From: Ragnar To: ALVARO ARCILA Cc: pgsql-performance@postgresql.org In-Reply-To: References: Content-Type: text/plain; charset=ISO-8859-1 Date: Wed, 20 Dec 2006 09:01:28 +0000 Message-Id: <1166605288.6369.274.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.8.1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200612/485 X-Sequence-Number: 22541 On miš, 2006-12-20 at 05:31 +0000, ALVARO ARCILA wrote: > > HI, > > I've looking around the log files of my server and lately they > indicate that I should consider increase the check_point segments > because they're beeing reading too often and also recommend increasing > the max_fsm_pages over 169728... if this has been happening for some time, some tables might possibly have become bloated with dead rows, so a one-time VACUUM FULL or CLUSTER on these might be indicated to speed up reaching the steady state. I think the max_fsm_pages is a minimum recommendation, so you might want to look at VACUUM VERBOSE output after setting it, to see if an even higher value is indicated > those are the config values present in the postgresql.conf > > shared_buffers = 1000 > work_mem = 8192 if you have got a lot of memory, you might want to experiment with these a little gnari