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

From Alvaro Herrera
Subject Re: [PATCH] Include application_name in "connection authorized" logmessage
Date
Msg-id 20180622192606.lsxo2l5nhixf5dk2@alvherre.pgsql
Whole thread Raw
In response to Re: [PATCH] Include application_name in "connection authorized" logmessage  (Andres Freund <andres@anarazel.de>)
Responses Re: [PATCH] Include application_name in "connection authorized" logmessage
List pgsql-hackers
On 2018-Jun-22, Andres Freund wrote:

> On 2018-06-22 12:16:18 -0400, Robert Haas wrote:

> > OK, that makes more sense, but I'm still skeptical of adding a special
> > case particularly for application_name.
> 
> 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.  And what about the
application changing it after the fact?  One idea would be to have a log
line designed specifically to be printed once at connection start (if
not log_connections) and then once immediately after it changes.  Am I
the only one for whom this sounds like overengineering?

I think the idea is nice, but I'm not sure about feasibility.

I further think that the idea in the OP is sound enough.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: sixela
Date:
Subject: Re: pg_verify_checksums review
Next
From: Andres Freund
Date:
Subject: Re: [PATCH] Include application_name in "connection authorized" logmessage