summaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2018-11-14 11:27:31 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2018-11-14 11:27:31 -0500
commit68f30638a050b5798f5947fe54a0ecb482203d05 (patch)
treeb219f643912ba9e53d8c840da1921c75e4e5e22a /doc/src
parent5793289c7a45f0cff06985aef49669b697435bf9 (diff)
Second try at fixing numeric data passed through an ECPG SQLDA.
In commit ecfd55795, I removed sqlda.c's checks for ndigits != 0 on the grounds that we should duplicate the state of the numeric value's digit buffer even when all the digits are zeroes. However, that still isn't quite right, because another possible state of the digit buffer is buf == digits == NULL (this occurs for a NaN). As the code now stands, it'll invoke memcpy with a NULL source address and zero bytecount, which we know a few platforms crash on. Hence, reinstate the no-copy short-circuit, but make it test specifically for buf != NULL rather than some other condition. In hindsight, the ndigits test (added by commit f2ae9f9c3) was almost certainly meant to fix the NaN case not the all-zeroes case as the associated thread alleged. As before, back-patch to all supported versions. Discussion: https://postgr.es/m/1803D792815FC24D871C00D17AE95905C71161@g01jpexmbkw24
Diffstat (limited to 'doc/src')
0 files changed, 0 insertions, 0 deletions