]> git.ipfire.org Git - thirdparty/postgresql.git/commit
Make "postgres -C guc" print "" not "(null)" for null-valued GUCs.
authorTom Lane <tgl@sss.pgh.pa.us>
Wed, 22 Jun 2016 15:55:18 +0000 (11:55 -0400)
committerTom Lane <tgl@sss.pgh.pa.us>
Wed, 22 Jun 2016 15:55:35 +0000 (11:55 -0400)
commitdd41661d2c613c3e4f8328191758398bfbcbd598
tree4ef903fbdc3e59adab8fb73d36882d39db0c8f90
parent85743887e847b187bb16ec1f0ca3b967bc124223
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