Re: pgsql: Fix deadlock hazard in CREATE INDEX CONCURRENTLY

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Fix deadlock hazard in CREATE INDEX CONCURRENTLY
Date: 2018-01-03 14:47:49
Message-ID: 20180103144749.mizihdcsmvtwl6qb@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Alvaro Herrera wrote:

> However this means that the test will get removed in 9.4 and 9.5 because
> isolationtester is not smart enough there.
>
> I suppose the other option would be to add an alternate expected file
> for the test.

Actually, so far only 9.6 and up have failed. Maybe the old
isolationtester is different enough that the other thing doesn't happen.

I'm more inclined now to add the alternate file instead of the other
patch.

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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2018-01-03 14:53:31 Re: pgsql: Fix deadlock hazard in CREATE INDEX CONCURRENTLY
Previous Message Alvaro Herrera 2018-01-03 14:27:00 Re: pgsql: Fix deadlock hazard in CREATE INDEX CONCURRENTLY