Re: Support for REINDEX CONCURRENTLY

Michael Paquier <michael.paquier@gmail.com>

From: Michael Paquier <michael.paquier@gmail.com>

To: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>

Cc: Peter Eisentraut <peter_e@gmx.net>, Fujii Masao <masao.fujii@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Simon Riggs <simon@2ndquadrant.com>, Andres Freund <andres@2ndquadrant.com>

Date: 2013-03-04T13:33:53Z

Lists: pgsql-hackers

Attachments

20130304_1_remove_reltoastidxid.patch (application/octet-stream) patch
20130304_2_reindex_concurrently_v16.patch (application/octet-stream) patch v16

Hi all,

Please find attached a patch fixing the last issue that Masao found with
make installcheck. Now REINDEX DATABASE CONCURRENTLY on the regression
database passes. There were 2 problems:
- Concurrent indexes for unique indexes using expressions were not
correctly created
- Concurrent indexes for indexes with duplicate column names were not
correctly created.
So, this solves the last issue currently on stack. I added some new tests
in regressions to cover those problems.

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 →

Background worker processes
- da07a1e85651 9.3.0 cited
Fix assorted bugs in CREATE/DROP INDEX CONCURRENTLY.
- 3c84046490be 9.3.0 cited
Work around unportable behavior of malloc(0) and realloc(NULL, 0).
- 09ac603c36d1 9.3.0 cited
Properly set relpersistence for fake relcache entries.
- beb850e1d873 9.3.0 cited