Re: [SPAM?]: Re: Support for REINDEX CONCURRENTLY - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: [SPAM?]: Re: Support for REINDEX CONCURRENTLY
Date
Msg-id CA+U5nM+Eq-wV0hO4aNqN=8dK1hS3pkH5tN4m=+w9pgmPY_2zcw@mail.gmail.com
Whole thread Raw
In response to Re: Support for REINDEX CONCURRENTLY  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: [SPAM?]: Re: Support for REINDEX CONCURRENTLY  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
On 10 December 2012 22:18, Peter Eisentraut <peter_e@gmx.net> wrote:
> On 12/8/12 9:40 AM, Tom Lane wrote:
>> I'm tempted to propose that REINDEX CONCURRENTLY simply not try to
>> preserve the index name exactly.  Something like adding or removing
>> trailing underscores would probably serve to generate a nonconflicting
>> name that's not too unsightly.
>
> If you think you can rename an index without an exclusive lock, then why
> not rename it back to the original name when you're done?

Because the index isn't being renamed. An alternate equivalent index
is being created instead.

-- Simon Riggs                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Support for REINDEX CONCURRENTLY
Next
From: Peter Eisentraut
Date:
Subject: Re: [SPAM?]: Re: Support for REINDEX CONCURRENTLY