pgsql: Fix some compiler warnings

Started by Michael Paquier7 months ago1 messagescomitters

michael@paquier.xyz

7 months ago

Fix some compiler warnings

Some of the buildfarm members with some old gcc versions have been
complaining about an always-true test for a NULL pointer caused by a
combination of SOFT_ERROR_OCCURRED() and a local ErrorSaveContext
variable.

These warnings are taken care of by removing SOFT_ERROR_OCCURRED(),
switching to a direct variable check, like 56b1e88c804b.

Oversights in e1405aa5e3ac and 44eba8f06e55.

Reported-by: Tom Lane <tgl@sss.pgh.pa.us>
Discussion: /messages/by-id/1341064.1764895052@sss.pgh.pa.us

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/7bc88c3d6f3af3af5330c0e209c8a3c411267d00

Modified Files
--------------
src/backend/utils/adt/pg_dependencies.c | 6 +++---
src/backend/utils/adt/pg_ndistinct.c | 4 ++--
2 files changed, 5 insertions(+), 5 deletions(-)