diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2015-08-02 15:48:27 -0400 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2015-08-02 15:48:31 -0400 |
commit | 13bba02271dce865cd20b6f49224889c73fed4e7 (patch) | |
tree | ded32b71f825f72b3a580e9a0b3553bc612975c1 /src/backend/executor/nodeFunctionscan.c | |
parent | cb3384a0cb4cf900622b77865f60e31259923079 (diff) | |
download | postgresql-13bba02271dce865cd20b6f49224889c73fed4e7.tar.gz postgresql-13bba02271dce865cd20b6f49224889c73fed4e7.zip |
Avoid calling memcpy() with a NULL source pointer and count == 0.
As in commit 0a52d378b03b7d5a, avoid doing something that has undefined
results according to the C standard, even though in practice there does
not seem to be any problem with it.
This fixes two places in numeric.c that demonstrably could call memcpy()
with such arguments. I looked through that file and didn't see any other
places with similar hazards; this is not to claim that there are not such
places in other files.
Per report from Piotr Stefaniak. Back-patch to 9.5 which is where the
previous commit was added. We're more or less setting a precedent that
we will not worry about this type of issue in pre-9.5 branches unless
someone demonstrates a problem in the field.
Diffstat (limited to 'src/backend/executor/nodeFunctionscan.c')
0 files changed, 0 insertions, 0 deletions