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

From Andres Freund
Subject Re: [PATCH] Include application_name in "connection authorized" logmessage
Date
Msg-id 20180622195316.27hqxaykxgmcgjr6@alap3.anarazel.de
Whole thread Raw
In response to Re: [PATCH] Include application_name in "connection authorized" logmessage  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: [PATCH] Include application_name in "connection authorized" logmessage
List pgsql-hackers
On 2018-06-22 15:50:06 -0400, Alvaro Herrera wrote:
> On 2018-Jun-22, Andres Freund wrote:
> 
> > On 2018-06-22 15:26:06 -0400, Alvaro Herrera wrote:
> > > On 2018-Jun-22, Andres Freund wrote:
> > > > I think a fair argument could be made that you'd want to have
> > > > application_name logged exactly once, not in every line. Just to cope
> > > > with log volume. With decent log analysis tools once is enough.
> > > 
> > > Seems harder than it sounds ... because if the user turns off
> > > log_connections then it's not longer in the log.
> > 
> > That's superuser only, so I really don't quite buy that argument.
> 
> I meant if the DBA disables it in postgresql.conf then the info is
> nowhere.

I'm not following - application_name isn't logged anywhere by default
currently either.


Greetings,

Andres Freund


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [PATCH] Include application_name in "connection authorized" logmessage
Next
From: Alvaro Herrera
Date:
Subject: Re: [PATCH] Include application_name in "connection authorized" logmessage