aboutsummaryrefslogtreecommitdiff
path: root/src/backend/parser/parse_utilcmd.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2015-12-13 14:52:07 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2015-12-13 14:52:07 -0500
commitfcbbf82d2b6caf7b156f2ec35b322e23caf1e99e (patch)
tree0e8ee4a0f1dae2d0e790f993dd2a38970204d3f0 /src/backend/parser/parse_utilcmd.c
parenta91bdf67c49ade2bdf6474607b64f9f0083db4a6 (diff)
downloadpostgresql-fcbbf82d2b6caf7b156f2ec35b322e23caf1e99e.tar.gz
postgresql-fcbbf82d2b6caf7b156f2ec35b322e23caf1e99e.zip
Code and docs review for multiple -c and -f options in psql.
Commit d5563d7df94488bf drew complaints from Coverity, which quite correctly complained that one copy of each -c or -f string was being leaked. What's more, simple_action_list_append was allocating enough space for still a third copy of each string as part of the SimpleActionListCell, even though that coding method had been superseded by a separate strdup operation. There were some other minor coding infelicities too. The documentation needed more work as well, eg it forgot to explain that -c causes psql not to accept any interactive input.
Diffstat (limited to 'src/backend/parser/parse_utilcmd.c')
0 files changed, 0 insertions, 0 deletions