aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/jsonpath_exec.c
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2024-09-09 13:49:59 +0900
committerMichael Paquier <michael@paquier.xyz>2024-09-09 13:49:59 +0900
commitcd6b2ae3e7f64c881cb0159a2f9fc8d475e06d82 (patch)
treebe0c23d702b71b15d13baf420e414dfc620dd411 /src/backend/utils/adt/jsonpath_exec.c
parente69030cb5178347d499bbc549213e950064564fa (diff)
downloadpostgresql-cd6b2ae3e7f64c881cb0159a2f9fc8d475e06d82.tar.gz
postgresql-cd6b2ae3e7f64c881cb0159a2f9fc8d475e06d82.zip
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
Diffstat (limited to 'src/backend/utils/adt/jsonpath_exec.c')
0 files changed, 0 insertions, 0 deletions