Re: Concurrently option for reindexdb

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(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-27 02:02:40
Message-ID: CAB7nPqT8B7DHTgMcTVZ4SGhQGAAUqBrdFin9VCd+D+7MtmhUxQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2014-08-27 02:04:03 Re: [RFC, POC] Don't require a NBuffer sized PrivateRefCount array of local buffer pins
Previous Message Peter Geoghegan 2014-08-27 02:01:39 Re: Similar to csvlog but not really, json logs?