Horton
Menu

Re: Support for REINDEX CONCURRENTLY

Simon Riggs <simon@2ndquadrant.com>

View thread
From: Simon Riggs <simon@2ndQuadrant.com>
To: Andres Freund <andres@2ndquadrant.com>
Cc: pgsql-hackers@postgresql.org, Michael Paquier <michael.paquier@gmail.com>
Date: 2012-10-03T08:33:31Z
Lists: pgsql-hackers 
On 3 October 2012 09:10, Andres Freund <andres@2ndquadrant.com> wrote:

>> The following restrictions are applied.
>> - REINDEX [ DATABASE | SYSTEM ] cannot be run concurrently.

> I would like to support something like REINDEX USER TABLES; or similar at some
> point, but that very well can be a second phase.

Yes, that would be a nice feature anyway, even without concurrently.

-- 
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

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.