diff options
| author | Michael Paquier <michael@paquier.xyz> | 2022-02-07 14:19:52 +0900 |
|---|---|---|
| committer | Michael Paquier <michael@paquier.xyz> | 2022-02-07 14:19:52 +0900 |
| commit | 42a9e88bf6a809e6023c9d50f58cc6b9446f229d (patch) | |
| tree | e78bb2d925c1eba2b65a2a1b3e2b80b7b54c3388 | |
| parent | 38bfae36526636ef55daf7cf2a3282403587cb5b (diff) | |
| download | postgresql-42a9e88bf6a809e6023c9d50f58cc6b9446f229d.tar.gz | |
Add (void) cast in front of rmtree() call at the end of pg_upgrade
Most calls of rmtree() report an error, and the code coming from 38bfae3
has introduced one caller where this is not done. The previous behavior
was to not fail hard if any log file generated is not properly unlinked
when cleaning up the contents generated once the upgrade has completed,
so add a cast to (void) to indicate the intention behind this new code.
Per gripe from Coverity.
| -rw-r--r-- | src/bin/pg_upgrade/pg_upgrade.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/bin/pg_upgrade/pg_upgrade.c b/src/bin/pg_upgrade/pg_upgrade.c index 48a54170a7..77beb11639 100644 --- a/src/bin/pg_upgrade/pg_upgrade.c +++ b/src/bin/pg_upgrade/pg_upgrade.c @@ -754,5 +754,5 @@ cleanup(void) /* Remove dump and log files? */ if (!log_opts.retain) - rmtree(log_opts.basedir, true); + (void) rmtree(log_opts.basedir, true); } |