Re: Support for REINDEX CONCURRENTLY

Michael Paquier <michael.paquier@gmail.com>

From: Michael Paquier <michael.paquier@gmail.com>
To: "anarazel@anarazel.de" <andres@anarazel.de>
Cc: Fujii Masao <masao.fujii@gmail.com>, Andres Freund <andres@2ndquadrant.com>, Tom Lane <tgl@sss.pgh.pa.us>, Simon Riggs <simon@2ndquadrant.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2013-02-28T08:00:00Z
Lists: pgsql-hackers
On Thu, Feb 28, 2013 at 4:56 PM, anarazel@anarazel.de <andres@anarazel.de>wrote:

> Hi,
>
> Michael Paquier <michael.paquier@gmail.com> schrieb:
>
> >Andres, Masao, do you need an extra round or review or do you think
> >this is
> >ready to be marked as committer?
> >On my side I have nothing more to add to the existing patches.
>
> I think they do need review before that - I won't be able to do another
> review before the weekend though.
>
Sure. Thanks.
-- 
Michael

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Background worker processes

  2. Fix assorted bugs in CREATE/DROP INDEX CONCURRENTLY.

  3. Work around unportable behavior of malloc(0) and realloc(NULL, 0).

  4. Properly set relpersistence for fake relcache entries.