Downgrade too verbose authentication logs.

When frontend authentication succeeds with clear text password and md5
authentication, message is out with log priority LOG. This floods
Pgpool-II log on busy systems. To fix this, downgrade the LOG message
to DEBUG1. Note that CERT auth related log level is still
LOG. Downgrading it causes regression 024 and 029 failure.

Discussion:
https://www.pgpool.net/mantisbt/view.php?id=606
https://www.pgpool.net/pipermail/pgpool-general/2020-April/007064.html

diff --git a/src/auth/pool_auth.c b/src/auth/pool_auth.c
index 8e385264e48f4b3fbd8a75706068d24dc30d3a95..d9e5dc90c3198ad967dff16191b79b05455faa41 100644 (file)
--- a/src/auth/pool_auth.c
+++ b/src/auth/pool_auth.c
@@ -994,7 +994,7 @@ authenticate_frontend_clear_text(POOL_CONNECTION * frontend)
                                (errmsg("clear text authentication failed"),
                                 errdetail("password does not match")));
        }
-       ereport(LOG,
+       ereport(DEBUG1,
                        (errmsg("clear text authentication successful with frontend")));
 
        if (frontend->passwordMapping->pgpoolUser.passwordType == PASSWORD_TYPE_AES)
@@ -1598,7 +1598,7 @@ authenticate_frontend_md5(POOL_CONNECTION * backend, POOL_CONNECTION * frontend,
                                (errmsg("md5 authentication failed"),
                                 errdetail("password does not match")));
        }
-       ereport(LOG,
+       ereport(DEBUG1,
                        (errmsg("md5 authentication successful with frontend")));
 
        frontend->frontend_authenticated = true;