Clarify RI tuple-lock result handling comments Explain that returning false for TM_SelfModified follows ExecLockRows(), which skips such tuples. This differs from TM_Updated, which is unexpected in READ COMMITTED with FIND_LAST_VERSION.
Also remove "fall through to error" from the TM_Updated comment, since the code calls elog(ERROR) directly. Reported-by: Amit Kapila <[email protected]> Discussion: https://postgr.es/m/caa4ek1lk1dfgifpl-hcczm-nm+exg+fcsodh8kpw6bobuzf...@mail.gmail.com Backpatch-through: 19 Branch ------ REL_19_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/ca3fd678f47becc5b84e0b027b2f062c5ad05b2b Modified Files -------------- src/backend/utils/adt/ri_triggers.c | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-)
