Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125])
	by mail.postgresql.org (Postfix) with ESMTP id C638717A223
	for <pgsql-sql@postgresql.org>; Thu,  9 Feb 2012 13:49:08 -0400 (AST)
Received: from sam.nabble.com ([216.139.236.26])
	by makus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <riyav@hotmail.com>) id 1RvY7I-00037p-5o
	for pgsql-sql@postgresql.org; Thu, 09 Feb 2012 17:49:08 +0000
Received: from [192.168.236.26] (helo=sam.nabble.com)
	by sam.nabble.com with esmtp (Exim 4.72)
	(envelope-from <riyav@hotmail.com>) id 1RvY73-0001eb-Ik
	for pgsql-sql@postgresql.org; Thu, 09 Feb 2012 09:48:53 -0800
Date: Thu, 9 Feb 2012 09:48:53 -0800 (PST)
From: rverghese <riyav@hotmail.com>
To: pgsql-sql@postgresql.org
Message-ID: <1328809733573-5470216.post@n5.nabble.com>
In-Reply-To: <jgueru$2vk$1@dough.gmane.org>
References: <1328724449781-5467243.post@n5.nabble.com>
	<jgueru$2vk$1@dough.gmane.org>
Subject: Re: Concurrent Reindex on Primary Key for large table
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Pg-Spam-Score: -0.1 (/)
X-Archive-Number: 201202/29
X-Sequence-Number: 36322

Thanks! That worked. 

Any thoughts about containing index bloat. I thought the autovac would clean
it up a bit more. Would any tweaks to my settings improve autovac
performance? I am still doing a couple of concurrent reindexes per week
otherwise performance degrades over a couple of days. 

Thanks
RV

--
View this message in context: http://postgresql.1045698.n5.nabble.com/Concurrent-Reindex-on-Primary-Key-for-large-table-tp5467243p5470216.html
Sent from the PostgreSQL - sql mailing list archive at Nabble.com.