Fix another oversight in logging of changes in postgresql.conf settings.
We were using GetConfigOption to collect the old value of each setting,
overlooking the possibility that it didn't exist yet. This does happen
in the case of adding a new entry within a custom variable class, as
exhibited in bug #6097 from Maxim Boguk.
To fix, add a missing_ok parameter to GetConfigOption, but only in 9.1
and HEAD --- it seems possible that some third-party code is using that
function, so changing its API in a minor release would cause problems.
In 9.0, create a near-duplicate function instead.
src/backend/commands/extension.c | 6 +++---
src/backend/utils/misc/guc-file.l | 6 +++---
src/backend/utils/misc/guc.c | 16 ++++++++++++----
src/include/utils/guc.h | 3 ++-
4 files changed, 20 insertions(+), 11 deletions(-)
pgsql-committers by date
|Next:||From: Tom Lane||Date: 2011-07-08 21:03:32|
|Subject: pgsql: Fix another oversight in logging of changes in postgresql.confs|
|Previous:||From: Heikki Linnakangas||Date: 2011-07-08 16:06:02|
|Subject: pgsql: Introduce a pipe between postmaster and each backend,which can |