Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit e45e990

Browse files
committed
Make "postgres -C guc" print "" not "(null)" for null-valued GUCs.
Commit 0b0baf2 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>
1 parent 6a9c518 commit e45e990

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/backend/postmaster/postmaster.c

+1-1
Original file line numberDiff line numberDiff line change
@@ -834,7 +834,7 @@ PostmasterMain(int argc, char *argv[])
834834
const char *config_val = GetConfigOption(output_config_variable,
835835
false, false);
836836

837-
puts(config_val ? config_val : "(null)");
837+
puts(config_val ? config_val : "");
838838
ExitPostmaster(0);
839839
}
840840

0 commit comments

Comments
 (0)