diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2018-12-26 16:08:17 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2018-12-26 16:08:17 -0500 |
| commit | 8528e3d849a896f8711c56fb41eae56f8c986729 (patch) | |
| tree | 8c5a1f303eeb4f5d872f80f285bc5b03c147eca4 /src/backend/parser/parse_utilcmd.c | |
| parent | e9fcfed3fb6b15e6b33bea9bb8504b14560857a8 (diff) | |
| download | postgresql-8528e3d849a896f8711c56fb41eae56f8c986729.tar.gz postgresql-8528e3d849a896f8711c56fb41eae56f8c986729.zip | |
Fix failure to check for open() or fsync() failures.
While it seems OK to not be concerned about fsync() failure for a
pre-existing signal file, it's not OK to not even check for open()
failure. This at least causes complaints from static analyzers,
and I think on some platforms passing -1 to fsync() or close() might
trigger assertion-type failures. Also add (void) casts to make clear
that we're ignoring fsync's result intentionally.
Oversights in commit 2dedf4d9a, noted by Coverity.
Diffstat (limited to 'src/backend/parser/parse_utilcmd.c')
0 files changed, 0 insertions, 0 deletions