Re: Avoiding deadlock errors in CREATE INDEX CONCURRENTLY

From: "Goel, Dhruv" <goeldhru(at)amazon(dot)com>
To: Thomas Munro <thomas(dot)munro(at)gmail(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-08 22:33:34
Message-ID: 9BA3CF6C-4448-4413-A125-18A29FDB759B@amazon.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

Thank you Thomas.

On Jul 7, 2019, at 3:15 PM, Thomas Munro <thomas(dot)munro(at)gmail(dot)com<mailto:thomas(dot)munro(at)gmail(dot)com>> wrote:

On Mon, Jul 8, 2019 at 9:51 AM Thomas Munro <thomas(dot)munro(at)gmail(dot)com<mailto: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
I have attached the revised patch. I ran check-world multiple times on my machine and it seems to succeed now. Do you mind kicking-off the CI build with the latest patch?

Attachment Content-Type Size
patch-cic.patch application/octet-stream 7.4 KB
ATT00001.htm text/html 309 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2019-07-08 22:37:19 Re: [PATCH] Incremental sort (was: PoC: Partial sort)
Previous Message Alexander Korotkov 2019-07-08 22:31:29 Re: [PATCH] Incremental sort (was: PoC: Partial sort)