Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commitdafdcbb

Browse files
committed
Make "postgres -C guc" print "" not "(null)" for null-valued GUCs.
Commit0b0baf2 et al made this case print "(null)" on the grounds thatthat's what happened on platforms that didn't crash. But neither behaviorwas actually intentional. What we should print is just an empty string,for compatibility with the behavior of SHOW and other ways of examiningstring 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 parent8df3c7b commitdafdcbb

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

‎src/backend/postmaster/postmaster.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -854,7 +854,7 @@ PostmasterMain(int argc, char *argv[])
854854
constchar*config_val=GetConfigOption(output_config_variable,
855855
false, false);
856856

857-
puts(config_val ?config_val :"(null)");
857+
puts(config_val ?config_val :"");
858858
ExitPostmaster(0);
859859
}
860860

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp