aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistxlog.c
diff options
context:
space:
mode:
authorStephen Frost <sfrost@snowman.net>2020-12-02 14:41:53 -0500
committerStephen Frost <sfrost@snowman.net>2020-12-02 14:41:53 -0500
commitdc11f31a1a891f8aa8890644e837556bcc5a75e7 (patch)
tree12346c9677a28b24f4eed258c7a167b0d83eb762 /src/backend/access/gist/gistxlog.c
parent01469241b2ff6f17fc0b3f20f01559145ffab29e (diff)
downloadpostgresql-dc11f31a1a891f8aa8890644e837556bcc5a75e7.tar.gz
postgresql-dc11f31a1a891f8aa8890644e837556bcc5a75e7.zip
Add GSS information to connection authorized log message
GSS information (if used) such as if the connection was authorized using GSS or if it was encrypted using GSS, and perhaps most importantly, what the GSS principal used for the authentication was, is extremely useful but wasn't being included in the connection authorized log message. Therefore, add to the connection authorized log message that information, in a similar manner to how we log SSL information when SSL is used for a connection. Author: Vignesh C Reviewed-by: Bharath Rupireddy Discussion: https://www.postgresql.org/message-id/CALDaNm2N1385_Ltoo%3DS7VGT-ESu_bRQa-sC1wg6ikrM2L2Z49w%40mail.gmail.com
Diffstat (limited to 'src/backend/access/gist/gistxlog.c')
0 files changed, 0 insertions, 0 deletions