Fix mishandling of background worker PGPROCs in EXEC_BACKEND builds.

robertmhaas · robertmhaas · commit e280c630a87e · 2014-07-30T11:34:06.000-04:00
InitProcess() relies on IsBackgroundWorker to decide whether the PGPROC
for a new backend should be taken from ProcGlobal's freeProcs or from
bgworkerFreeProcs.  In EXEC_BACKEND builds, InitProcess() is called
sooner than in non-EXEC_BACKEND builds, and IsBackgroundWorker wasn't
getting initialized soon enough.

Report by Noah Misch.  Diagnosis and fix by me.
diff --git a/src/backend/postmaster/postmaster.c b/src/backend/postmaster/postmaster.c
@@ -4668,6 +4668,9 @@ SubPostmasterMain(int argc, char *argv[])
 	{
 		int			shmem_slot;
 
+		/* do this as early as possible; in particular, before InitProcess() */
+		IsBackgroundWorker = true;
+
 		/* Close the postmaster's sockets */
 		ClosePostmasterPorts(false);
 

Original file line number	Diff line number	Diff line change
`@@ -4668,6 +4668,9 @@ SubPostmasterMain(int argc, char *argv[])`
`4668`	`4668`	`{`
`4669`	`4669`	`int shmem_slot;`
`4670`	`4670`
	`4671`	`+ /* do this as early as possible; in particular, before InitProcess() */`
	`4672`	`+ IsBackgroundWorker = true;`
	`4673`	`+`
`4671`	`4674`	`/* Close the postmaster's sockets */`
`4672`	`4675`	`ClosePostmasterPorts(false);`
`4673`	`4676`