Re: pgsql: Fix potential assertion failure when reindexing a pg_class index

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Fix potential assertion failure when reindexing a pg_class index
Date: 2019-04-30 13:28:30
Message-ID: 17514.1556630910@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> writes:
> There seem to be a number of regression test failures involving deadlock
> resulting from this. e.g. on prion:

Yeah, see -hackers thread: <20190430070552(dot)jzqgcy4ihalx7nur(at)alap3(dot)anarazel(dot)de>

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2019-04-30 14:37:10 pgsql: Widen tuple counter variables from long to int64
Previous Message Andrew Dunstan 2019-04-30 12:24:56 Re: pgsql: Fix potential assertion failure when reindexing a pg_class index