From: Michael Paquier <michael@paquier.xyz>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: James Coleman <jtc331@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: [DOC] Document concurrent index builds waiting on each other
Date: Mon, 30 Sep 2019 10:24:06 +0900
Message-ID: <20190930012406.GC2888@paquier.xyz> (raw)
In-Reply-To: <20190929012228.GA21412@alvherre.pgsql>
References: <20190928161838.GD26853@momjian.us>
<20190929012228.GA21412@alvherre.pgsql>
On Sat, Sep 28, 2019 at 10:22:28PM -0300, Alvaro Herrera wrote:
> I always thought that create index concurrently was prevented from
> running concurrently in a table by the ShareUpdateExclusive lock that's
> held during the operation.
REINDEX CONCURRENTLY and CIC can deadlock while waiting for each other
to finish after their validation phase, see:
https://www.postgresql.org/message-id/20190507030756.GD1499@paquier.xyzhttps://www.postgresql.org/message-id/20190507032543.GH1499@paquier.xyz
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: michael@paquier.xyz, alvherre@2ndquadrant.com, bruce@momjian.us, jtc331@gmail.com
Subject: Re: [DOC] Document concurrent index builds waiting on each other
In-Reply-To: <20190930012406.GC2888@paquier.xyz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox