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:51 -0400 |
commit | c75b1f75b3d159c0e71c1ec7f42c922bce448d89 (patch) | |
tree | b3364ce26279a4c35524795218b2d073ce3ca575 /src/backend/executor | |
parent | ea8385df6ce95507951f6c12fa4defb5b3ba9cda (diff) | |
download | postgresql-c75b1f75b3d159c0e71c1ec7f42c922bce448d89.tar.gz postgresql-c75b1f75b3d159c0e71c1ec7f42c922bce448d89.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')
0 files changed, 0 insertions, 0 deletions