aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/execMain.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2009-10-03 18:04:57 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2009-10-03 18:04:57 +0000
commit54d60bbd075a61c7dd2ef384dc930d726d68ee64 (patch)
treee42859f4f1d4da1b83497ce59fd2b4713abc0035 /src/backend/executor/execMain.c
parent66a8417f4e595fe72bf610f58fa013823f00cb47 (diff)
downloadpostgresql-54d60bbd075a61c7dd2ef384dc930d726d68ee64.tar.gz
postgresql-54d60bbd075a61c7dd2ef384dc930d726d68ee64.zip
Fix a couple of issues in recent patch to print updates to postgresql.conf
settings: avoid calling superuser() in contexts where it's not defined, don't leak the transient copies of GetConfigOption output, and avoid the whole exercise in postmaster child processes. I found that actually no current caller of GetConfigOption has any use for its internal check of GUC_SUPERUSER_ONLY. But rather than just remove that entirely, it seemed better to add a parameter indicating whether to enforce the check. Per report from Simon and subsequent testing.
Diffstat (limited to 'src/backend/executor/execMain.c')
0 files changed, 0 insertions, 0 deletions