public inbox for [email protected]  

help / color / mirror / Atom feed

From: Robert Haas <[email protected]>
To: Alvaro Herrera <[email protected]>
Cc: Greg Smith <[email protected]>
Cc: pgsql-docs <[email protected]>
Subject: Re: Improve warnings around CREATE INDEX CONCURRENTLY
Date: Mon, 13 Jun 2011 12:11:48 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On Thu, May 26, 2011 at 11:52 AM, Alvaro Herrera
<[email protected]> wrote:
> Excerpts from Greg Smith's message of mié may 25 17:04:03 -0400 2011:
>
>> 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.
>
> Great
>
>> Back to the doc patch I submitted...is that a useful step toward making
>> this issue visible enough to users for now to help?
>
> Sure, why not?  I thought I could choose my bikeshed color while I was
> here, how about
>
> +    second and third transaction.  All active transactions at the time the
> +    second table scan starts, not just ones that already involve the table,
> +    have the potential to block the concurrent index creation until they
> +    finish.  When checking for transactions that
> +    could still use the original index, concurrent index creation advances
> +    through potentially interfering older transactions one at a time,
> +    obtaining shared locks on their virtual transaction identifiers to wait for
> +    them to complete.

Alvaro, did you commit this?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

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], [email protected], [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