Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 392B99FB600 for ; Tue, 5 Jun 2007 21:22:21 -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 91551-04 for ; Tue, 5 Jun 2007 21:22:18 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by postgresql.org (Postfix) with ESMTP id C506A9FB56B for ; Tue, 5 Jun 2007 21:22:20 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.13.8/8.13.8) with ESMTP id l560MCsC055090 for ; Tue, 5 Jun 2007 21:22:13 -0300 (ADT) (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.13.8/8.13.8/Submit) id l55NxHI6031394 for pgsql-admin@postgresql.org; Tue, 5 Jun 2007 20:59:17 -0300 (ADT) (envelope-from news) From: "Charles.Hou" X-Newsgroups: pgsql.admin Subject: Re: the right time to vacuum database? Date: Tue, 05 Jun 2007 16:59:21 -0700 Organization: http://groups.google.com Lines: 25 Message-ID: <1181087961.969587.237660@g37g2000prf.googlegroups.com> References: <1181039589.643323.59660@r19g2000prf.googlegroups.com> <1181049167.27654.55.camel@dba5.int.libertyrms.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Complaints-To: groups-abuse@google.com In-Reply-To: <1181049167.27654.55.camel@dba5.int.libertyrms.com> User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727),gzip(gfe),gzip(gfe) X-HTTP-Via: 1.0 y6p_proxy:3128 (squid) Complaints-To: groups-abuse@google.com Injection-Info: g37g2000prf.googlegroups.com; posting-host=59.125.145.5; posting-account=Mznd-A0AAABITZ14OcULoTm5bpaBaOsm To: pgsql-admin@postgresql.org X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200706/35 X-Sequence-Number: 25703 On 6 5 , 9 12 , bnich...@ca.afilias.info (Brad Nicholson) wrote: > On Tue, 2007-06-05 at 03:33 -0700, Charles.Hou wrote: > > how can i know that it's the time to vacuumdb? i set the crontab to > > vacuumdb 3 times in one day. because my database size increase from > > 440MB to 460MB in 8 hours. > > Have you looked at autovaccum? It can handle this for you. > > If not, you need to examine the output of VACUUM VERBOSE or pg_stattuple > (in contrib) and set a policy based on the output. > > It's entirely possible that some tables will need to get vacuumed > frequently, and others will not. > > -- > Brad Nicholson 416-673-4106 > Database Administrator, Afilias Canada Corp. > > ---------------------------(end of broadcast)--------------------------- > TIP 3: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faq where is the contrib directory? i can't find it.