diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2018-02-02 18:32:05 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2018-02-02 18:32:05 -0500 |
| commit | d59ff4ab3111f20054425d82dab1393101dcfe8e (patch) | |
| tree | d75ba05547d48b26998d6b875ee77f69afcecb13 /src/backend/executor/nodeMergeAppend.c | |
| parent | 957ff087c822c95f63df956e1a91c15614ecb2b4 (diff) | |
| download | postgresql-d59ff4ab3111f20054425d82dab1393101dcfe8e.tar.gz postgresql-d59ff4ab3111f20054425d82dab1393101dcfe8e.zip | |
Fix another instance of unsafe coding for shm_toc_lookup failure.
One or another author of commit 5bcf389ec seems to have thought that
computing an offset from a NULL pointer would yield another NULL pointer.
There may possibly be architectures where that works, but common machines
don't work like that. Per a quick code review of places calling
shm_toc_lookup and not using noError = false.
Diffstat (limited to 'src/backend/executor/nodeMergeAppend.c')
0 files changed, 0 insertions, 0 deletions