Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id CD350B5DBE0 for ; Tue, 24 May 2011 17:48:20 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 04807-08 for ; Tue, 24 May 2011 20:48:13 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from spinlock.commandprompt.com (host-215.commandprompt.net [207.173.203.215]) by mail.postgresql.org (Postfix) with ESMTP id 8E117B5DBDA for ; Tue, 24 May 2011 17:48:13 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by spinlock.commandprompt.com (Postfix) with ESMTP id EAE12348045; Tue, 24 May 2011 13:48:12 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at commandprompt.com Received: from spinlock.commandprompt.com ([127.0.0.1]) by localhost (spinlock.commandprompt.com.commandprompt.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PtI+m6SwT+ho; Tue, 24 May 2011 13:48:11 -0700 (PDT) Received: from perhan.alvh.no-ip.org (unknown [200.85.213.137]) by spinlock.commandprompt.com (Postfix) with ESMTPSA id CC516348044; Tue, 24 May 2011 13:48:10 -0700 (PDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 245796E3EC; Tue, 24 May 2011 16:48:07 -0400 (CLT) Content-Type: text/plain; charset=UTF-8 Cc: pgsql-docs Subject: Re: Improve warnings around CREATE INDEX CONCURRENTLY From: Alvaro Herrera To: Greg Smith In-reply-to: <4DDB64CB.7070109@2ndQuadrant.com> References: <4DDB64CB.7070109@2ndQuadrant.com> Date: Tue, 24 May 2011 16:48:07 -0400 Message-Id: <1306269968-sup-2890@alvh.no-ip.org> User-Agent: Sup/git Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-5 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201105/79 X-Sequence-Number: 6754 Excerpts from Greg Smith's message of mar may 24 03:56:59 -0400 2011: > What makes it worse is that the wait shows up as a virtualxid one, which > doesn't pop up on many common samples of things to look for in > pg_locks. It would be reasonable but also incorrect for admins to > assume a table one would be visible if running into the case alluded to > in the docs. The serial way locks are obtained is unexpected too. Incidentally, this is one of the things that Jim Nasby wanted exposed somehow so that these problems are more easily diagnosed. I dropped the ball on that one, but I'll be picking it up again at some point. -- Álvaro Herrera The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support