diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2021-01-28 17:18:23 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2021-01-28 17:18:42 -0500 |
| commit | c4484232ed3f17c270621eb8ffb974d85023b9ea (patch) | |
| tree | 30a690d813636a0c30a464846b9b048b6231ac37 /src/backend/executor/nodeHashjoin.c | |
| parent | 46371600aa2dac11ce6a8bcc314e5e037fb7ff9c (diff) | |
| download | postgresql-c4484232ed3f17c270621eb8ffb974d85023b9ea.tar.gz postgresql-c4484232ed3f17c270621eb8ffb974d85023b9ea.zip | |
Silence another gcc 11 warning.
Per buildfarm and local experimentation, bleeding-edge gcc isn't
convinced that the MemSet in reorder_function_arguments() is safe.
Shut it up by adding an explicit check that pronargs isn't negative,
and by changing MemSet to memset. (It appears that either change is
enough to quiet the warning at -O2, but let's do both to be sure.)
Diffstat (limited to 'src/backend/executor/nodeHashjoin.c')
0 files changed, 0 insertions, 0 deletions