Message-ID: <4DDD6EC3.80703@2ndQuadrant.com>
Date: Wed, 25 May 2011 17:04:03 -0400
From: Greg Smith <greg@2ndQuadrant.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
	rv:1.9.1.16) Gecko/20110505 Icedove/3.0.11
MIME-Version: 1.0
CC: pgsql-docs <pgsql-docs@postgresql.org>
Subject: Re: Improve warnings around CREATE INDEX CONCURRENTLY
References: <4DDB64CB.7070109@2ndQuadrant.com>
	<1306269968-sup-2890@alvh.no-ip.org>
	<4DDC1DBF.3050306@2ndQuadrant.com>
	<1306346092-sup-2903@alvh.no-ip.org>
In-Reply-To: <1306346092-sup-2903@alvh.no-ip.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 05/25/2011 01:57 PM, Alvaro Herrera wrote:
> Please see this thread:
> http://archives.postgresql.org/message-id/1290465663-sup-9908@alvh.no-ip.org
>    

Ah, now I see--I was running a CommitFest that week, so of course I 
missed this message.  Those are all good ideas.

>> 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.
>    

Sure.  Simon's command string idea might work better, and doing some 
extra lock decoration as you suggested in the above thread would be 
another level of improvement.  We should pick up redesign later on the 
main list.  You can at least count me in as someone who wants to see 
this improved now.

Back to the doc patch I submitted...is that a useful step toward making 
this issue visible enough to users for now to help?

-- 
Greg Smith   2ndQuadrant US    greg@2ndQuadrant.com   Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support  www.2ndQuadrant.us