Re: Support for REINDEX CONCURRENTLY

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>
Subject: Re: Support for REINDEX CONCURRENTLY
Date: 2013-03-04 13:33:53
Message-ID: CAB7nPqQyFmhg-yrKVPGj0uEKT0xYsVReoAyVYWp-BH5WghAKUA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

Attachment Content-Type Size
20130304_1_remove_reltoastidxid.patch application/octet-stream 39.2 KB
20130304_2_reindex_concurrently_v16.patch application/octet-stream 75.2 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Euler Taveira 2013-03-04 13:37:32 Re: Materialized views WIP patch
Previous Message Andres Freund 2013-03-04 12:53:42 Re: Status of the startup process post end of recovery