diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2019-11-05 14:27:37 -0500 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2019-11-05 14:27:37 -0500 |
commit | f9bd3b6d929aa731ef5b999c9fadfc2acd0b7cfe (patch) | |
tree | 6eb62934be661b9ce0ec2cca13b0e4809487734f /src/backend/utils/adt/misc.c | |
parent | 791864193636764b4cbba0acd2b4eab7581eb2c3 (diff) | |
download | postgresql-f9bd3b6d929aa731ef5b999c9fadfc2acd0b7cfe.tar.gz postgresql-f9bd3b6d929aa731ef5b999c9fadfc2acd0b7cfe.zip |
Avoid logging complaints about abandoned connections when using PAM.
For a long time (since commit aed378e8d) we have had a policy to log
nothing about a connection if the client disconnects when challenged
for a password. This is because libpq-using clients will typically
do that, and then come back for a new connection attempt once they've
collected a password from their user, so that logging the abandoned
connection attempt will just result in log spam. However, this did
not work well for PAM authentication: the bottom-level function
pam_passwd_conv_proc() was on board with it, but we logged messages
at higher levels anyway, for lack of any reporting mechanism.
Add a flag and tweak the logic so that the case is silent, as it is
for other password-using auth mechanisms.
Per complaint from Yoann La Cancellera. It's been like this for awhile,
so back-patch to all supported branches.
Discussion: https://postgr.es/m/CACP=ajbrFFYUrLyJBLV8=q+eNCapa1xDEyvXhMoYrNphs-xqPw@mail.gmail.com
Diffstat (limited to 'src/backend/utils/adt/misc.c')
0 files changed, 0 insertions, 0 deletions