Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id D0FE99FA173 for ; Wed, 6 Dec 2006 11:59:58 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-new, port 10024) with ESMTP id 95450-09 for ; Wed, 6 Dec 2006 11:59:51 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from mail.socialserve.com (office.socialserve.com [208.60.89.34]) by postgresql.org (Postfix) with ESMTP id 4BF859F9FDA for ; Wed, 6 Dec 2006 11:59:52 -0400 (AST) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.socialserve.com (Postfix) with ESMTP id 85883396ABD for ; Wed, 6 Dec 2006 10:59:40 -0500 (EST) X-Virus-Scanned: by amavisd-new at socialserve.com Received: from mail.socialserve.com ([127.0.0.1]) by localhost (ms3.socialserve.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RSXIM16WPNf0 for ; Wed, 6 Dec 2006 10:59:39 -0500 (EST) Received: from [10.1.1.43] (jlrobins.socialserve.com [10.1.1.43]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.socialserve.com (Postfix) with ESMTP id 520F4396ABC for ; Wed, 6 Dec 2006 10:59:39 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v752.2) Content-Transfer-Encoding: 7bit Message-Id: <5F277D5E-DB72-4BA1-9DFA-175FB749FB21@socialserve.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: pgsql-docs@postgresql.org From: James Robinson Subject: create index concurrently docs ... Date: Wed, 6 Dec 2006 10:59:48 -0500 X-Mailer: Apple Mail (2.752.2) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200612/24 X-Sequence-Number: 3947 In reading over the caveats regarding create index concurrently, I think it'd be nice to see an example of what the return result will be if an 'invalid' index is created so a dba who read the docs night recognize the error, as well as for searchengine fodder to find out what to do real fast if such an error happens to them. Something around this paragraph in http://www.postgresql.org/docs/ current/static/sql-createindex.html#SQL-CREATEINDEX-CONCURRENTLY: "If a problem arises during the second scan of the table, such as a uniqueness violation in a unique index, the CREATE INDEX command will fail but leave behind an "invalid" index." Thanks! ---- James Robinson Socialserve.com