aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/transam/commit_ts.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2016-01-07 11:19:33 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2016-01-07 11:19:33 -0500
commit5e0b5dcab685fe2a342385450a29a825cf40cddf (patch)
tree8d33859039f9edeb829f78ffb5413b3ea70e1cdc /src/backend/access/transam/commit_ts.c
parenta967613911f7ef7b6387b9e8718f0ab8f0c4d9c8 (diff)
downloadpostgresql-5e0b5dcab685fe2a342385450a29a825cf40cddf.tar.gz
postgresql-5e0b5dcab685fe2a342385450a29a825cf40cddf.zip
Provide more detail in postmaster log for password authentication failures.
We tell people to examine the postmaster log if they're unsure why they are getting auth failures, but actually only a few relatively-uncommon failure cases were given their own log detail messages in commit 64e43c59b817a78d. Expand on that so that every failure case detected within md5_crypt_verify gets a specific log detail message. This should cover pretty much every ordinary password auth failure cause. So far I've not noticed user demand for a similar level of auth detail for the other auth methods, but sooner or later somebody might want to work on them. This is not that patch, though.
Diffstat (limited to 'src/backend/access/transam/commit_ts.c')
0 files changed, 0 insertions, 0 deletions