Re: Index corruption with CREATE INDEX CONCURRENTLY

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Index corruption with CREATE INDEX CONCURRENTLY
Date: 2017-02-05 13:03:07
Message-ID: CAB7nPqReFFvJ5Qsf+wP3SZ7PDZi6UMTVXtBfywuH3JQ1erVakg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Feb 5, 2017 at 6:53 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> I agree with Pavan - a release with known important bug is not good idea.

This bug has been around for some time, so I would recommend taking
the time necessary to make the best fix possible, even if it means
waiting for the next round of minor releases.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip Kumar 2017-02-05 14:48:51 Re: Parallel bitmap heap scan
Previous Message Amit Kapila 2017-02-05 10:35:17 Re: Draft release notes for next week's releases are up for review