From: Tom Lane <tgl@sss.pgh.pa.us>
To: Japin Li <japinli@hotmail.com>
cc: pgsql-sql@postgresql.org
Subject: Re: Could not use index because of indcheckxmin is true
In-reply-to: 
 <MEYP282MB16694E0A76DD574FE7A31BC8B6D3A@MEYP282MB1669.AUSP282.PROD.OUTLOOK.COM>
References: 
 <MEYP282MB16694E0A76DD574FE7A31BC8B6D3A@MEYP282MB1669.AUSP282.PROD.OUTLOOK.COM>
Comments: In-reply-to Japin Li <japinli@hotmail.com>
	message dated "Thu, 12 Oct 2023 15:06:17 +0800"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1025274.1697121002.1@sss.pgh.pa.us>
Date: Thu, 12 Oct 2023 10:30:02 -0400
Message-ID: <1025275.1697121002@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1025275.1697121002%40sss.pgh.pa.us>
Precedence: bulk

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.

			regards, tom lane