public inbox for [email protected]
help / color / mirror / Atom feedFrom: Greg Smith <[email protected]>
Cc: pgsql-docs <[email protected]>
Subject: Re: Improve warnings around CREATE INDEX CONCURRENTLY
Date: Wed, 25 May 2011 17:04:03 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
On 05/25/2011 01:57 PM, Alvaro Herrera wrote:
> Please see this thread:
> http://archives.postgresql.org/message-id/[email protected]
>
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 [email protected] Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us
view thread (10+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected]
Subject: Re: Improve warnings around CREATE INDEX CONCURRENTLY
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox