X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org
Received: from localhost (av.hub.org [200.46.204.144])
	by svr1.postgresql.org (Postfix) with ESMTP id BBD8CDAD8E
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Tue, 25 Oct 2005 10:56:05 -0300 (ADT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 36718-04
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Tue, 25 Oct 2005 13:56:01 +0000 (GMT)
Received: from web31615.mail.mud.yahoo.com (web31615.mail.mud.yahoo.com
	[68.142.198.161])
	by svr1.postgresql.org (Postfix) with SMTP id 842B4DADA0
	for <pgsql-performance@postgresql.org>;
	Tue, 25 Oct 2005 10:56:03 -0300 (ADT)
Received: (qmail 39808 invoked by uid 60001); 25 Oct 2005 13:56:07 -0000
Message-ID: <20051025135607.39805.qmail@web31615.mail.mud.yahoo.com>
Received: from [209.217.70.195] by web31615.mail.mud.yahoo.com via HTTP;
	Tue, 25 Oct 2005 06:56:07 PDT
Date: Tue, 25 Oct 2005 06:56:07 -0700 (PDT)
From: Markus Benne <thing@m-bass.com>
Reply-To: markus@m-bass.com
Subject: Reindex - Is this necessary after a vacuum?
To: pgsql-performance@postgresql.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, hits=0 required=5 tests=[none]
X-Spam-Level: 
X-Archive-Number: 200510/359
X-Sequence-Number: 15127

We are reindexing frequently, and I'm wondering if
this is really necessary, given that it appears to
take an exclusive lock on the table.

Our table in question is vacuumed every 4 minutes, and
we are reindexing after each one.

I'm not a fan of locking this table that frequently,
even if it is only for 5 - 10 seconds depending on
load.

The vacuum is a standard vacuum.  Nightly we do a
vacuum analyze.

Thanks for any tips,
...Markus