Sender: smw@sabre.com
Message-ID: <37F8F2BE.760A4087@sabre.com>
Date: Mon, 04 Oct 1999 13:32:31 -0500
From: "Steven M. Wheeler" <swheeler@sabre.com>
Organization: Mid-range UNIX Engineering, The SABRE Group
MIME-Version: 1.0
To: Tom Lane <tgl@sss.pgh.pa.us>
CC: pgsql-sql@hub.org
Subject: Re: [SQL] Questions about vacuum analyze
References: <20576.938814148@sss.pgh.pa.us>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Tom,

I believe that 6.5.2 and a little space reclamation in my DB directory may
have taken care of the vacuum problem.  The last vacuum ran in about 10
minutes on an already vacuumed DB.  I am now loading another 400K inserts
and will perform the vacuum again at the conclusion.  A couple of questions
remain.

1) With 6.5.2 should I still drop the indexes prior to running vacuum?

2) Is there a command/script that will cleanup the temp files and previous
table files in the DB directory.  The reason I ask: I now have 3 copies of
my currnt table file (currnt, currnt.1, currnt.2) for a total usage of
about 3GB.  Since it appears that currnt.2 is the one being accessed, can I
safely delete currnt & currnt.1?

Thanks again for all the help!

--
Steven Wheeler
Mid-Range UNIX Engineering
Sabre Inc.
(918) 292-4119

Tom Lane wrote:

> "Steven M. Wheeler" <swheeler@sabre.com> writes:
> > DB: version 6.5
> > 33 hours [to vacuum] - WOW!
>
> Yipes.  We did find and fix a glitch in memory allocation in vacuum
> (causing both slowness and excessive memory usage) between 6.5 and
> 6.5.2.  You might try updating to see if it's gotten any better...
>
>                         regards, tom lane