aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist
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:28 -0400
commitf22a3e5ce1237936422471a05cf0776c266034cf (patch)
tree3e2070df43b09494444af4c6384aa1e8d3c30d68 /src/backend/access/gist
parente251b26065615247e9054e1996e7372d18e7311c (diff)
downloadpostgresql-f22a3e5ce1237936422471a05cf0776c266034cf.tar.gz
postgresql-f22a3e5ce1237936422471a05cf0776c266034cf.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')
0 files changed, 0 insertions, 0 deletions