Fix unsafe usage of strerror(errno) within ereport().

This is the converse of the unsafe-usage-of-%m problem: the reason
ereport/elog provide that format code is mainly to dodge the hazard
of errno getting changed before control reaches functions within the
arguments of the macro.  I only found one instance of this hazard,
but it's been there since 9.4 :-(.

diff --git a/src/backend/libpq/auth.c b/src/backend/libpq/auth.c
index be8c4776859601f076fb2c7f6ba263e3976ea8b0..9c77701785f32fff5d44a7d5394c9c3f01459b35 100644 (file)
--- a/src/backend/libpq/auth.c
+++ b/src/backend/libpq/auth.c
@@ -1752,10 +1752,12 @@ auth_peer(hbaPort *port)
        pw = getpwuid(uid);
        if (!pw)
        {
+               int                     save_errno = errno;
+
                ereport(LOG,
                                (errmsg("could not look up local user ID %ld: %s",
                                                (long) uid,
-                                               errno ? strerror(errno) : _("user does not exist"))));
+                                               save_errno ? strerror(save_errno) : _("user does not exist"))));
                return STATUS_ERROR;
        }