aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands/functioncmds.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2011-07-21 12:24:14 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2011-07-21 12:24:14 -0400
commita9f0dbc39df88ea7672352d3e7070d2603491bec (patch)
tree7a929fe088ddc62425948eafa4b552c8c2041237 /src/backend/commands/functioncmds.c
parent0ce7676aa03a2501fde949fea211ba5cd84c2ded (diff)
downloadpostgresql-a9f0dbc39df88ea7672352d3e7070d2603491bec.tar.gz
postgresql-a9f0dbc39df88ea7672352d3e7070d2603491bec.zip
Fix PQsetvalue() to avoid possible crash when adding a new tuple.
PQsetvalue unnecessarily duplicated the logic in pqAddTuple, and didn't duplicate it exactly either --- pqAddTuple does not care what is in the tuple-pointer array positions beyond the last valid entry, whereas the code in PQsetvalue assumed such positions would contain NULL. This led to possible crashes if PQsetvalue was applied to a PGresult that had previously been enlarged with pqAddTuple, for instance one built from a server query. Fix by relying on pqAddTuple instead of duplicating logic, and not assuming anything about the contents of res->tuples[res->ntups]. Back-patch to 8.4, where PQsetvalue was introduced. Andrew Chernow
Diffstat (limited to 'src/backend/commands/functioncmds.c')
0 files changed, 0 insertions, 0 deletions