Re: Concurrently option for reindexdb

From: Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Concurrently option for reindexdb
Date: 2014-09-01 11:13:32
Message-ID: CAD21AoAf7fVDR+TPxd5mrK-9MLOAKeUkkXT0dgW1cHeExXHhuw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Aug 27, 2014 at 11:02 AM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> On Tue, Aug 26, 2014 at 5:12 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
>> On 2014-08-26 12:44:43 +0900, Michael Paquier wrote:
>> I always was of the opinion that a exclusive lock is still *MUCH* better
>> than what we have today.
> Well, if somebody has some interest in that, here is a rebased patch
> with the approach using low-level locks:
> http://www.postgresql.org/message-id/CAB7nPqRkwKFgn4BFUybqU-Oo-=Gcbq0K-8H93Gr6fX-GGRPDXg@mail.gmail.com

My patch need to be improved doc and to be renamed option name
(--minimum-locks?)
Also I need to test, e.g., foreign key and primary key.

Anyway, If REINDEX CONCURRENTLY patch Michael submitted is committed then
I might need to rebase the patch (rather it's not necessary..?)
So I will see how it goes for a while.

Regards,

-------
Sawada Masahiko

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2014-09-01 11:14:41 Re: Immediate standby promotion
Previous Message Craig Ringer 2014-09-01 11:08:22 Adding 'crosstab' variants returning refcursor?