diff options
| author | Tom Lane | 2016-06-22 15:55:18 +0000 |
|---|---|---|
| committer | Tom Lane | 2016-06-22 15:55:18 +0000 |
| commit | e45e990e4b547f05bdb46e4596d24abbaef60043 (patch) | |
| tree | 18d8f42a96a1d5f155b63a1cf11614b6b468ed3f | |
| parent | 6a9c51810f1db08de4033cbecd95a83d7b364fd1 (diff) | |
Make "postgres -C guc" print "" not "(null)" for null-valued GUCs.
Commit 0b0baf262 et al made this case print "(null)" on the grounds that
that's what happened on platforms that didn't crash. But neither behavior
was actually intentional. What we should print is just an empty string,
for compatibility with the behavior of SHOW and other ways of examining
string GUCs. Those code paths don't distinguish NULL from empty strings,
so we should not here either. Per gripe from Alain Radix.
Like the previous patch, back-patch to 9.2 where -C option was introduced.
Discussion: <CA+YdpwxPUADrmxSD7+Td=uOshMB1KkDN7G7cf+FGmNjjxMhjbw@mail.gmail.com>
| -rw-r--r-- | src/backend/postmaster/postmaster.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/postmaster/postmaster.c b/src/backend/postmaster/postmaster.c index e350dd29252..19d11e0e0da 100644 --- a/src/backend/postmaster/postmaster.c +++ b/src/backend/postmaster/postmaster.c @@ -834,7 +834,7 @@ PostmasterMain(int argc, char *argv[]) const char *config_val = GetConfigOption(output_config_variable, false, false); - puts(config_val ? config_val : "(null)"); + puts(config_val ? config_val : ""); ExitPostmaster(0); } |