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

On Thu, Jun 07, 2007 at 12:07:03AM -0700, Charles.Hou wrote:
> 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.

Maybe it was doing work.  Why did you kill it?  If there is a problem
on that table, I wouldn't be surprised that it'd take 10 minutes. 
You just caused all the work it started to do to be undone, and to
cause more bloat.  But. . .

> DETAIL:  0 dead row versions cannot be removed yet.

. . . this suggests you don't have bloat on that table at least.  So
it sounds to me like your disk use is going up because you have a lot
of data.

A

-- 
Andrew Sullivan  | ajs@crankycanuck.ca
In the future this spectacle of the middle classes shocking the avant-
garde will probably become the textbook definition of Postmodernism. 
                --Brad Holland