Re: Avoiding deadlock errors in CREATE INDEX CONCURRENTLY

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: "Goel, Dhruv" <goeldhru(at)amazon(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Kuntal Ghosh <kuntalghosh(dot)2007(at)gmail(dot)com>
Subject: Re: Avoiding deadlock errors in CREATE INDEX CONCURRENTLY
Date: 2019-07-07 22:15:48
Message-ID: CA+hUKGJSwGVz7Y2xiKZGERK=bP6DWUCswtwxKJPhhPj6-dJc_Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jul 8, 2019 at 9:51 AM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> I noticed that check-world passed several times with this patch
> applied, but the most recent CI run failed in multiple-cic:
>
> +error in steps s2i s1i: ERROR: cache lookup failed for index 26303
>
> https://travis-ci.org/postgresql-cfbot/postgresql/builds/555472214

And in another run, this time on Windows, create_index failed:

https://ci.appveyor.com/project/postgresql-cfbot/postgresql/build/1.0.46455

--
Thomas Munro
https://enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2019-07-07 22:47:06 Re: Control your disk usage in PG: Introduction to Disk Quota Extension
Previous Message Thomas Munro 2019-07-07 22:07:02 Re: dropdb --force