Fix using injection points at backend startup in EXEC_BACKEND mode
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>
Fri, 26 Jul 2024 11:55:04 +0000 (14:55 +0300)
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>
Fri, 26 Jul 2024 12:11:50 +0000 (15:11 +0300)
commitb9e5249c29354186576d8fc00609fe7eaf7c8d25
tree7827efe3eb46d439df6c7d549c18b8ca6d17678d
parentc95d2159c1dd3f269383a9bd830e1c804dba34c8
Fix using injection points at backend startup in EXEC_BACKEND mode

Commit 86db52a506 changed the locking of injection points to use only
atomic ops and spinlocks, to make it possible to define injection
points in processes that don't have a PGPROC entry (yet). However, it
didn't work in EXEC_BACKEND mode, because the pointer to shared memory
area was not initialized until the process "attaches" to all the
shared memory structs. To fix, pass the pointer to the child process
along with other global variables that need to be set up early.

Backpatch-through: 17
src/backend/postmaster/launch_backend.c
src/backend/utils/misc/injection_point.c
src/include/utils/injection_point.h