aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeFunctionscan.c
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2023-06-11 10:33:59 +0900
committerMichael Paquier <michael@paquier.xyz>2023-06-11 10:33:59 +0900
commit9920552e1e4e5b5a203f2444f71202d7d46782f8 (patch)
tree45f057b26a995b05231af8a23f1f6dcba6b2f298 /src/backend/executor/nodeFunctionscan.c
parent3509a060d7311b7f9904e011fd9574732a8c81b2 (diff)
downloadpostgresql-9920552e1e4e5b5a203f2444f71202d7d46782f8.tar.gz
postgresql-9920552e1e4e5b5a203f2444f71202d7d46782f8.zip
Fix missing initializations of MyProc.delayChkptEnd
This commit fixes an oversight introduced in 10520f4, that has added delayChkptEnd to PGPROC to avoid ABI breakages on stable branches, where two spots have missed to initialize this variable (delayChkpt was switched back from int to bool, and it was initialized as 0 so there was no consequences for it): - InitProcess(), where the per-process data structures of a backend are initialized. - InitAuxiliaryProcess(), same but for auxiliary processes. An interruption during relation truncation while this flag is set could cause an assertion failure when a follow-up process does a relation truncation while reusing the same PGPROC entry. A second effect could be incorrect checkpoint end delays. While on it, add an assertion in ProcArrayClearTransaction() for delayChkptEnd to be in line with 5788e25. This is needed only for v14. This issue affects v11~v14, but not v15~, as we use a single field called delayChkptFlags to delay checkpoints there. Author: suyu.cmj (mengjuan.cmj@alibaba-inc.com) Reviewed-by: Kyotaro Horiguchi, Michael Paquier Discussion: https://postgr.es/m/9c3d2a49-db5f-43cb-840b-d58f9a684295.mengjuan.cmj@alibaba-inc.com Backpatch-through: 11
Diffstat (limited to 'src/backend/executor/nodeFunctionscan.c')
0 files changed, 0 insertions, 0 deletions