Re: Index corruption with CREATE INDEX CONCURRENTLY

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Index corruption with CREATE INDEX CONCURRENTLY
Date: 2017-02-06 12:32:28
Message-ID: 20170206123228.au5eotrdwafor5to@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund wrote:

> To show what I mean here's an *unpolished* and *barely tested* patch
> implementing the first of my suggestions.
>
> Alvaro, Pavan, I think should address the issue as well?

Hmm, interesting idea. Maybe a patch along these lines is a good way to
make index-list cache less brittle going forward. However, I'm against
putting it in the stable branches -- and we should definitely not stall
an immediate fix in order to get this patch ready. IMO we should get
Tom's patch in tree for all branches very soon, and then after the
release you can finalize this one and put it to master.

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2017-02-06 12:55:08 SCRAM authentication, take three
Previous Message Alvaro Herrera 2017-02-06 12:13:46 Re: Index corruption with CREATE INDEX CONCURRENTLY