| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Concurrently option for reindexdb |
| Date: | 2014-08-25 20:35:20 |
| Message-ID: | 20140825203520.GA6343@eldon.alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Paquier wrote:
> On Tue, Aug 26, 2014 at 3:48 AM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> > On Mon, Aug 25, 2014 at 4:33 PM, Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-08-25 20:46:10 | Re: Concurrently option for reindexdb |
| Previous Message | Alvaro Herrera | 2014-08-25 20:33:43 | Re: Add CREATE support to event triggers |