From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Fix processing of PGC_BACKEND GUC parameters on Windows. |
Date: | 2014-04-05 16:42:07 |
Message-ID: | E1WWTfT-0000Sq-9B@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
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_3_STABLE
Details
-------
http://git.postgresql.org/pg/commitdiff/18db2150cee092a0b85baf41c27b800bafa1b480
Modified Files
--------------
src/backend/utils/misc/guc.c | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2014-04-05 19:17:08 | pgsql: Fix another palloc in critical section. |
Previous Message | Tom Lane | 2014-04-05 06:20:42 | pgsql: ecpg/ecpglib must build the src/port files it uses with -DFRONTE |