Re: [PATCH] Include application_name in "connection authorized" log message - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: [PATCH] Include application_name in "connection authorized" log message
Date
Msg-id CAOuzzgqbONNyUiuH_uQhF75h-1NOw-=zwBaFU+45HRUKggccWg@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Include application_name in "connection authorized" log message  (Don Seiler <don@seiler.us>)
Responses Re: [PATCH] Include application_name in "connection authorized" logmessage
List pgsql-hackers
Greetings

On Mon, Jun 25, 2018 at 15:57 Don Seiler <don@seiler.us> wrote:
On Mon, Jun 25, 2018 at 10:50 AM, Gilles Darold <gilles.darold@dalibo.com> wrote:
I would prefer the following output to conform to elog.c output:

    2018-06-25 17:32:46.854 CEST [23265] LOG:  connection authorized: user=postgres database=postgres application=[unknown]

Hello Gilles,

The different cases were for Stephen's request earlier in this thread. I'm happy to write it either way and agree it would be nice to not have a lot of duplicate code. Do you want me to submit another patch?

I think it’s better to not change the line when application name isn’t being set, as the latest patch has. That also matches how we handle the SSL info- it’s only shown if ssl is in place on the connection. 

Thanks!

Stephen

pgsql-hackers by date:

Previous
From: Don Seiler
Date:
Subject: Re: [PATCH] Include application_name in "connection authorized" log message
Next
From: Gilles Darold
Date:
Subject: Re: [PATCH] Include application_name in "connection authorized" logmessage