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>
This commit is contained in:
parent
7a349889ec
commit
f2c28bb1f2
|
@ -828,7 +828,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);
|
||||
}
|
||||
|
||||
|
|
Loading…
Reference in New Issue