Re: Support for REINDEX CONCURRENTLY

Michael Paquier <michael.paquier@gmail.com>

From: Michael Paquier <michael.paquier@gmail.com>
To: Fujii Masao <masao.fujii@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-06T04:29:41Z
Lists: pgsql-hackers

Attachments

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

Those patches have been generated with context diffs...
Regards,
-- 
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.