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-08 23:22:21
Message-ID: CA+hUKG+0m2i6L1oY_bHSQD3A8KPWjaS4i15YgS_oq9X1Hj=u0g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jul 9, 2019 at 10:33 AM Goel, Dhruv <goeldhru(at)amazon(dot)com> wrote:
> 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?

Thanks.

It's triggered automatically when you post patches to the thread and
also once a day, though it took ~35 minutes to get around to noticing
your new version due to other activity in other threads, and general
lack of horsepower. I'm planning to fix that with more horses.

It passed on both OSes. See here:

http://cfbot.cputube.org/dhruv-goel.html

--
Thomas Munro
https://enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2019-07-08 23:27:12 Re: [Proposal] Table-level Transparent Data Encryption (TDE) and Key Management Service (KMS)
Previous Message Thomas Munro 2019-07-08 22:54:44 Re: Two pg_rewind patches (auto generate recovery conf and ensure clean shutdown)