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

From Alvaro Herrera
Subject Re: Concurrently option for reindexdb
Date
Msg-id 20140825203520.GA6343@eldon.alvh.no-ip.org
Whole thread Raw
In response to Re: Concurrently option for reindexdb  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: Concurrently option for reindexdb
List pgsql-hackers
Michael Paquier wrote:
> 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.

Why not just finish up the REINDEX CONCURRENTLY patch.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Add CREATE support to event triggers
Next
From: Andres Freund
Date:
Subject: Re: Concurrently option for reindexdb