Date: Wed, 6 Jun 2007 15:51:01 -0400
From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-admin@postgresql.org
Subject: Re: the right time to vacuum database?
Message-ID: <20070606195101.GF11545@phlogiston.dyndns.org>
References: <1181039589.643323.59660@r19g2000prf.googlegroups.com>
	<20070605132546.GI4818@phlogiston.dyndns.org>
	<1181089690.963738.260660@n15g2000prd.googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1181089690.963738.260660@n15g2000prd.googlegroups.com>
User-Agent: Mutt/1.5.9i

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?  

A


-- 
Andrew Sullivan  | ajs@crankycanuck.ca
The whole tendency of modern prose is away from concreteness.
		--George Orwell