Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 4120212822D8 for ; Wed, 22 Feb 2012 17:07:35 -0400 (AST) Received: from sam.nabble.com ([216.139.236.26]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1S0JPR-0006LR-0O for pgsql-sql@postgresql.org; Wed, 22 Feb 2012 21:07:34 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1S0JPE-0004bR-F5 for pgsql-sql@postgresql.org; Wed, 22 Feb 2012 13:07:20 -0800 Date: Wed, 22 Feb 2012 13:07:20 -0800 (PST) From: rverghese To: pgsql-sql@postgresql.org Message-ID: <1329944840460-5506261.post@n5.nabble.com> In-Reply-To: References: <1328724449781-5467243.post@n5.nabble.com> 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/74 X-Sequence-Number: 36367 Hi I had another question, what about when the primary key is a foreign key in another table? Is the only option to drop the FK and recreate it after the primary key has been created with the new index? Thanks! RV -- View this message in context: http://postgresql.1045698.n5.nabble.com/Concurrent-Reindex-on-Primary-Key-for-large-table-tp5467243p5506261.html Sent from the PostgreSQL - sql mailing list archive at Nabble.com.