Re: Avoiding deadlock errors in CREATE INDEX CONCURRENTLY - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Avoiding deadlock errors in CREATE INDEX CONCURRENTLY
Date
Msg-id 804334B1-C93F-40E0-99AA-B21EEC05B556@anarazel.de
Whole thread Raw
In response to Re: Avoiding deadlock errors in CREATE INDEX CONCURRENTLY  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Avoiding deadlock errors in CREATE INDEX CONCURRENTLY
List pgsql-hackers
Hi,

On June 9, 2019 8:36:37 AM PDT, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>"Goel, Dhruv" <goeldhru@amazon.com> writes:
>I think you are mistaken that doing transactional updates in pg_index
>is OK.  If memory serves, we rely on xmin of the pg_index row for
>purposes
>such as detecting whether a concurrently-created index is safe to use
>yet.

We could replace that with storing a 64 xid in a normal column nowadays.

Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Avoiding deadlock errors in CREATE INDEX CONCURRENTLY
Next
From: Avinash Kumar
Date:
Subject: Re: Bloom Indexes - bit array length and the total number of bits (orhash functions ?? ) !