Received: from nsi.edu (amethea.nsi.edu [198.133.185.9])
	by hub.org (8.9.2/8.9.1) with ESMTP id NAA38437
	for <pgsql-sql@hub.org>; Wed, 10 Mar 1999 13:42:27 -0500 (EST)
	(envelope-from reina@nsi.edu)
Received: from nsi.edu (IDENT:reina@bigred.nsi.edu [204.128.156.214])
	by nsi.edu (8.9.1/8.9.1) with ESMTP id KAA25912;
	Wed, 10 Mar 1999 10:42:21 -0800 (PST)
Sender: reina@nsi.edu
Message-ID: <36E6BD8E.F0B7B4B3@nsi.edu>
Date: Wed, 10 Mar 1999 18:44:30 +0000
From: "G. Anthony Reina" <reina@nsi.edu>
Organization: The Neurosciences Institute
X-Mailer: Mozilla 4.5 [en] (X11; U; Linux 2.2.1 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Jason Slagle <raistlin@tacorp.net>
CC: pgsql-sql@hub.org
Subject: Re: [SQL] Performance
References: <Pine.LNX.4.03.9903101327030.20770-100000@tacorp.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Jason Slagle wrote:

> And how long is normal for Vacuum analyze to take on bout 350 megs of
> DATA?
>
> Jason
>

My database is 1.4 Gig. It takes about 2-3 minutes for a vacuum analyze verbose.
I have had problems in the past with a corrupted main index (the table of
tables). In such a case, the vacuum never stops even after > 48 hours. Try
vacuuming your tables one-by-one if you have really long vaccums (> 1 hour). If
the tables vacuum one-by-one alright, then you have a corrupted main index.

-Tony