Fix processing of PGC_BACKEND GUC parameters on Windows.
EXEC_BACKEND builds (i.e., Windows) failed to absorb values of PGC_BACKEND
parameters if they'd been changed post-startup via the config file. This
for example prevented log_connections from working if it were turned on
post-startup. The mechanism for handling this case has always been a bit
of a kluge, and it wasn't revisited when we implemented EXEC_BACKEND.
While in a normal forking environment new backends will inherit the
postmaster's value of such settings, EXEC_BACKEND backends have to read
the settings from the CONFIG_EXEC_PARAMS file, and they were mistakenly
rejecting them. So this case has always been broken in the Windows port;
so back-patch to all supported branches.
Amit Kapila
Branch
------
REL9_1_STABLE
Details
-------
http://git.postgresql.org/pg/commitdiff/cb11f4d8d5d7fd171621b8ee6262cd42bc4e9e07
Modified Files
--------------
src/backend/utils/misc/guc.c | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)