Hello! On Mon, Nov 3, 2025 at 12:21 AM Noah Misch <[email protected]> wrote: > Thanks. Does "ON CONFLICT ON CONSTRAINT constraint_name" avoid the problem w/ > concurrent REINDEX CONCURRENTLY? A search of the thread found no mention of > "ON CONSTRAINT". It seems safe to assume that clause would avoid problems w/ > CREATE INDEX CONCURRENTLY, but that's less certain for REINDEX.
It is also affected. There is a special reindex_concurrently_upsert_on_constraint spec in the patch. And even a special commit (0004) to fix it :) But yes, it happens only in the case of REINDEX. I removed the mention of "ON CONSTRAINT" and added a small comment near infer_arbiter_indexes. Doc patch is 0001, other - specs and fixes for future. Best regards, Mikhail.
v11-0002-Specs-to-reproduce-the-issues-with-CREATE-INDEX-.patch
Description: Binary data
v11-0005-Modify-the-ExecInitPartitionInfo-function-to-con.patch
Description: Binary data
v11-0003-Modify-the-infer_arbiter_indexes-function-to-con.patch
Description: Binary data
v11-0006-Revert-Doc-cover-index-CONCURRENTLY-causing-erro.patch
Description: Binary data
v11-0004-Modify-the-infer_arbiter_indexes-function-to-als.patch
Description: Binary data
v11-0001-Doc-cover-index-CONCURRENTLY-causing-errors-in-I.patch
Description: Binary data
