aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistutil.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2016-06-22 11:55:18 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2016-06-22 11:55:24 -0400
commitf2c28bb1f2fee6fa33d2d6d4316b3f1d499543a4 (patch)
tree72122530623f755daba4711c15ad753fd876777d /src/backend/access/gist/gistutil.c
parent7a349889ec1e80123f475fb171640b8273f921fd (diff)
downloadpostgresql-f2c28bb1f2fee6fa33d2d6d4316b3f1d499543a4.tar.gz
postgresql-f2c28bb1f2fee6fa33d2d6d4316b3f1d499543a4.zip
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>
Diffstat (limited to 'src/backend/access/gist/gistutil.c')
0 files changed, 0 insertions, 0 deletions