X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id A97959FA42B for ; Mon, 15 May 2006 17:13:14 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 41160-02 for ; Mon, 15 May 2006 17:13:04 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id 12EC89FA15C for ; Mon, 15 May 2006 17:13:03 -0300 (ADT) Received: by noel.decibel.org (Postfix, from userid 1001) id 8EFB956423; Mon, 15 May 2006 15:13:02 -0500 (CDT) Received: (hashcash-sendmail, from uid 1001); Mon, 15 May 2006 15:13:01 -0500 Date: Mon, 15 May 2006 15:13:01 -0500 From: "Jim C. Nasby" To: "Xu, Xiaoyi (Rocky) FSM" Cc: andy.shellam@mailnetwork.co.uk, pgsql-admin@postgresql.org Subject: Re: Error in MS Access Message-ID: <20060515201301.GK26212@pervasive.com> References: <20060515194228.GH26212@pervasive.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 6.0-RELEASE-p4 amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.11 X-Hashcash: 1:20:060515:xyxu@northwestern.edu::ohMBORwND1hcKfn+:0000000000000000 00000000000000000000000001Ag X-Hashcash: 1:20:060515:andy.shellam@mailnetwork.co.uk::yoM8BKC48IuCGdyK:0000000 0000000000000000000000000dpC X-Hashcash: 1:20:060515:pgsql-admin@postgresql.org::HRHR9ueppYaXOtJZ:00000000000 0000000000000000000000007940 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/199 X-Sequence-Number: 21731 On Mon, May 15, 2006 at 02:55:04PM -0500, Xu, Xiaoyi (Rocky) FSM wrote: > Jim, > > I will find out the detailed version. Meanwhile /home0 is around 8.6 GB. > I don't know how large the DB is. Which file or which command I should > look for? About vacuuming, I don't know either. Can I do vacuuming while > making DB online? I am helping an internal department whose IT person > left and for 5 months no one ever managed this Solaris box. All of > sudden database users began to experience problems with an in-house > application. If it's anything newer than 7.2 (and I really hope it's a *lot* newer than that), then yes, you can vacuum without locking users out. I know that at some point you couldn't do that, but I don't know how long ago that was since I started using PostgreSQL at version 7.2. I suspect that no one has been vacuuming the database and that it now has scads of dead rows. It's surprising users haven't been screaming about it being slow before now if that's the case. If you search for 'vacuum' at http://www.pervasivepostgres.com/instantkb13/search.aspx you'll find some articles that might help you. -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461