postgres.git / summary / log / commit / refs

commit    f2c28bb1f2fee6fa33d2d6d4316b3f1d499543a4
Author:   Tom Lane <tgl@sss.pgh.pa.us>
Date:     Wed Jun 22 15:55:18 2016 +0000

    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>


 src/backend/postmaster/postmaster.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/backend/postmaster/postmaster.c b/src/backend/postmaster/postmaster.c
index 3cfd5b8a57e..c576986c6b2 100644
--- a/src/backend/postmaster/postmaster.c
+++ b/src/backend/postmaster/postmaster.c
@@ -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);
 	}
 


[parent: 7a349889ec1e]