Fix waits of REINDEX CONCURRENTLY for indexes with predicates or expressions
authorMichael Paquier <[email protected]>
Mon, 9 Sep 2024 04:50:16 +0000 (13:50 +0900)
committerMichael Paquier <[email protected]>
Mon, 9 Sep 2024 04:50:16 +0000 (13:50 +0900)
commit9021515488dd8f2dc43b7eaca127e113346f0449
treeea820723dced2310bb50efb176da8d26b85a2300
parent2534cd999e673b4e4a3c52233bbee5496a3c4b06
Fix waits of REINDEX CONCURRENTLY for indexes with predicates or expressions

As introduced by f9900df5f94, a REINDEX CONCURRENTLY job done for an
index with predicates or expressions would set PROC_IN_SAFE_IC in its
MyProc->statusFlags, causing it to be ignored by other concurrent
operations.

Such concurrent index rebuilds should never be ignored, as a predicate
or an expression could call a user-defined function that accesses a
different table than the table where the index is rebuilt.

A test that uses injection points is added, backpatched down to 17.
Michail has proposed a different test, but I have added something
simpler with more coverage.

Oversight in f9900df5f949.

Author: Michail Nikolaev
Discussion: https://postgr.es/m/CANtu0oj9A3kZVduFTG0vrmGnKB+DCHgEpzOp0qAyOgmks84j0w@mail.gmail.com
Backpatch-through: 14
src/backend/commands/indexcmds.c