Horton
Menu

Re: Support for REINDEX CONCURRENTLY

Fujii Masao <masao.fujii@gmail.com>

View thread
From: Fujii Masao <masao.fujii@gmail.com>
To: Michael Paquier <michael.paquier@gmail.com>
Cc: Andres Freund <andres@anarazel.de>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, Peter Eisentraut <peter_e@gmx.net>, Tom Lane <tgl@sss.pgh.pa.us>, Simon Riggs <simon@2ndquadrant.com>
Date: 2013-06-16T19:20:03Z
Lists: pgsql-hackers 
On Thu, Jun 6, 2013 at 1:29 PM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> Hi all,
>
> Please find attached the latest versions of REINDEX CONCURRENTLY for the 1st
> commit fest of 9.4:
> - 20130606_1_remove_reltoastidxid_v9.patch, removing reltoastidxid, to allow
> a toast relation to have multiple indexes running in parallel (extra indexes
> could be created by a REINDEX CONCURRENTLY processed)
> - 20130606_2_reindex_concurrently_v26.patch, correcting some comments and
> fixed a lock in index_concurrent_create on an index relation not released at
> the end of a transaction

Could you let me know how this patch has something to do with MVCC catalog
access patch? Should we wait for MVCC catalog access patch to be committed
before starting to review this patch?

Regards,

-- 
Fujii Masao

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.