Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 7E67C9FB302 for ; Thu, 7 Jun 2007 04:22:49 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 08266-01 for ; Thu, 7 Jun 2007 04:22:49 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by postgresql.org (Postfix) with ESMTP id 15E589FB2FD for ; Thu, 7 Jun 2007 04:22:49 -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 l577MgUa088502 for ; Thu, 7 Jun 2007 04:22:45 -0300 (ADT) (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.13.8/8.13.8/Submit) id l57773wC084445 for pgsql-admin@postgresql.org; Thu, 7 Jun 2007 04:07:03 -0300 (ADT) (envelope-from news) From: "Charles.Hou" X-Newsgroups: pgsql.admin Subject: Re: the right time to vacuum database? Date: Thu, 07 Jun 2007 00:07:03 -0700 Organization: http://groups.google.com Lines: 44 Message-ID: <1181200023.281625.249120@n15g2000prd.googlegroups.com> References: <1181039589.643323.59660@r19g2000prf.googlegroups.com> <20070605132546.GI4818@phlogiston.dyndns.org> <1181089690.963738.260660@n15g2000prd.googlegroups.com> <20070606195101.GF11545@phlogiston.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Complaints-To: groups-abuse@google.com In-Reply-To: <20070606195101.GF11545@phlogiston.dyndns.org> 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: n15g2000prd.googlegroups.com; posting-host=210.202.3.132; posting-account=Mznd-A0AAABITZ14OcULoTm5bpaBaOsm To: pgsql-admin@postgresql.org X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200706/65 X-Sequence-Number: 25733 On 6 7 , 3 51 , a...@crankycanuck.ca (Andrew Sullivan) wrote: > On Tue, Jun 05, 2007 at 05:28:10PM -0700, Charles.Hou wrote: > > Client connected: about 100 pc, 1 pc with 1 connection at least, the > > max is 4 connections > > So up to 400 connections? Are they all running transactions? For > any length of time? > > > 194 tables on the database, and some of the tables always executed > > the update/insert command . > > So _some_ tables are getting updated? (Inserts are not really > relevant to vacuuming here, but they'll surely be relevant to size) > > > i also set the autovacuum to enable. today, the database size is > > 497MB. 497-440MB=57MB, 57 MB have been increased in 18 hours. > > what's wrong with my PostgreSql Server? > > Maybe nothing. How much data do you think you're putting in there? > What does VACUUM VERBOSE say, as I asked about -- are you getting a > lot of dead space? > i use the VACUUM VERBOSE a table , but it had been hold 10 minutes . i must use the linux command " kill " to exit the VACUUM. after i kill this PID, the PostgreSql have been restart automatically. and vacuum result of the other table INFO: vacuuming "public.trade_rpt" INFO: "ftrade_rpt": found 987 removable, 117279 nonremovable row versions in 16875 pages DETAIL: 0 dead row versions cannot be removed yet. Nonremovable row versions range from 324 to 1280 bytes long. There were 9 unused item pointers. Total free space (including removable row versions) is 9059076 bytes. 138 pages are or will become empty, including 0 at the end of the table. 15838 pages containing 8772044 free bytes are potential move destinations. CPU 0.01s/0.00u sec elapsed 341.61 sec. 341.61sec???