Re: Could not use index because of indcheckxmin is true - Mailing list pgsql-sql

From Japin Li
Subject Re: Could not use index because of indcheckxmin is true
Date
Msg-id MEYP282MB166969CC0F50558A8E4AE486B6D3A@MEYP282MB1669.AUSP282.PROD.OUTLOOK.COM
Whole thread Raw
In response to Re: Could not use index because of indcheckxmin is true  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-sql
On Thu, 12 Oct 2023 at 22:30, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Japin Li <japinli@hotmail.com> writes:
>> When I create an index using CREATE INDEX (without concurrently), I get
>> an index which indcheckxmin is true.  According to the docs[1], it cannot
>> be used with indcheckxmin is ture, how can I fix this?
>
> There is nothing to fix; you just wait a little bit.
>
>>> indcheckxmin bool
>>> If true, queries must not use the index until the xmin of this pg_index
>>> row is below their TransactionXmin event horizon, because the table may
>>> contain broken HOT chains with incompatible rows that they can see
>
> Note the "until" clause.  Once transactions that ran concurrently
> with the CREATE INDEX are done, the index is available for use.
> There is no need for anyone to clear the indcheckxmin flag, and
> AFAIR there is no code that does so.
>

Thanks for your explanation. After wait a moment, the index can be used.

-- 
Regrads,
Japin Li



pgsql-sql by date:

Previous
From: Tom Lane
Date:
Subject: Re: Could not use index because of indcheckxmin is true
Next
From: Shaozhong SHI
Date:
Subject: stored procedures