Re: Concurrently option for reindexdb - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Concurrently option for reindexdb
Date
Msg-id CAB7nPqTfDrvyboLi4A+G-7E8ySF556oyiy=aSjqovSBPUy8Ajw@mail.gmail.com
Whole thread Raw
In response to Re: Concurrently option for reindexdb  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: Concurrently option for reindexdb
List pgsql-hackers
On Tue, Aug 26, 2014 at 3:48 AM, Fujii Masao <masao.fujii@gmail.com> wrote:
> On Mon, Aug 25, 2014 at 4:33 PM, Sawada Masahiko <sawada.mshk@gmail.com> wrote:
>> this might be difficult to call this as --concurrently.
>> It might need to be change the name.
>
> I'm OK to say that as --concurrently if the document clearly
> explains that restriction. Or --almost-concurrently? ;P
By reading that I am thinking as well about a wording with "lock",
like --minimum-locks.
-- 
Michael



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Set new system identifier using pg_resetxlog
Next
From: Michael Paquier
Date:
Subject: Re: Add CREATE support to event triggers