Content-Type: text/plain; charset=UTF-8
Cc: pgsql-docs <pgsql-docs@postgresql.org>
Subject: Re: Improve warnings around CREATE INDEX CONCURRENTLY
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Greg Smith <greg@2ndquadrant.com>
In-reply-to: <4DDC1DBF.3050306@2ndQuadrant.com>
References: <4DDB64CB.7070109@2ndQuadrant.com>
	<1306269968-sup-2890@alvh.no-ip.org>
	<4DDC1DBF.3050306@2ndQuadrant.com>
Date: Wed, 25 May 2011 13:57:19 -0400
Message-Id: <1306346092-sup-2903@alvh.no-ip.org>
User-Agent: Sup/git
Content-Transfer-Encoding: 8bit

Excerpts from Greg Smith's message of mar may 24 17:06:07 -0400 2011:
> On 05/24/2011 04:48 PM, Alvaro Herrera wrote:

> > 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.
> 
> I don't remember seeing anything about that before, but then again I 
> wasn't really looking for it until now.  Did you have a basic idea what 
> you wanted to do there?  I have enough of this work queued up now that I 
> may end up poking at the code myself here soon.

Please see this thread:
http://archives.postgresql.org/message-id/1290465663-sup-9908@alvh.no-ip.org

> The first thing I was considering was dropping some DEBUG2 level logging 
> about the various phases of the reindex into there.

That would take this system more or less to where autovacuum was in 8.1
(well, not quite that bad because you can change it locally, but still).
It seems to me we can do something a bit better than that.

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support