Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id BED8B9F9C51 for ; Tue, 28 Aug 2007 17:14:19 -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 42301-03-3 for ; Tue, 28 Aug 2007 17:14:10 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from Mercury.turbocorp.com (mercury.turbocorp.com [198.212.166.40]) by postgresql.org (Postfix) with ESMTP id 8B7DC9FA1BD for ; Tue, 28 Aug 2007 17:14:14 -0300 (ADT) Received: from [198.212.166.61] (Voyager.turbocorp.com [198.212.166.61]) by Mercury.turbocorp.com (8.13.1/8.13.1) with ESMTP id l7SKE9op023910; Tue, 28 Aug 2007 16:14:09 -0400 Message-ID: <46D48211.8010806@the-allgoods.net> Date: Tue, 28 Aug 2007 16:14:09 -0400 From: John R Allgood User-Agent: Thunderbird 1.5.0.12 (X11/20070718) MIME-Version: 1.0 To: Andrew Sullivan CC: pgsql-admin@postgresql.org Subject: Re: How to monitor resources on Linux. References: <46D4353F.2040209@the-allgoods.net> <815.1188324416@sss.pgh.pa.us> <46D470D8.2030605@the-allgoods.net> <20070828191143.GE13868@alvh.no-ip.org> <46D47A13.3060907@the-allgoods.net> <20070828195554.GB1683@phlogiston.dyndns.org> In-Reply-To: <20070828195554.GB1683@phlogiston.dyndns.org> Content-Type: multipart/alternative; boundary="------------040107070003040508000602" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/361 X-Sequence-Number: 26692 This is a multi-part message in MIME format. --------------040107070003040508000602 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit We were running vacuum and vacuum full daily without the vaccum analyze on weekends. After about 2 weeks the master database would slow down. How often do you run VACUUM or are you using the autovacumm daemon. Andrew Sullivan wrote: > On Tue, Aug 28, 2007 at 03:40:03PM -0400, John R Allgood wrote: > >> lot of activity as compared to the other databases. We run VACUUM at >> midday VACUUM FULL at night, VACUUM ANALYZE on weekends. >> > > If you are running VACUUM often enough, then you should _never_ need > VACUUM FULL. And weekly VACUUM ANALYSE is probably too infrequent. > > A > > --------------040107070003040508000602 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit We were running vacuum and vacuum full daily without the vaccum analyze on weekends. After about 2 weeks the master database would slow down. How often do you run VACUUM or are you using the autovacumm daemon.

Andrew Sullivan wrote:
On Tue, Aug 28, 2007 at 03:40:03PM -0400, John R Allgood wrote:
  
lot of activity as compared to the other databases. We run VACUUM at 
midday VACUUM FULL at night, VACUUM ANALYZE on weekends.
    

If you are running VACUUM often enough, then you should _never_ need
VACUUM FULL.  And weekly VACUUM ANALYSE is probably too infrequent. 

A

  

--------------040107070003040508000602--