Re: [PATCH] Include application_name in "connection authorized" log message

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Don Seiler <don(at)seiler(dot)us>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [PATCH] Include application_name in "connection authorized" log message
Date: 2018-07-13 08:11:51
Message-ID: 30ecd2ed-e779-1e5e-5acd-0297a3367fc3@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 02.07.18 15:12, Don Seiler wrote:
> On Mon, Jul 2, 2018 at 2:13 AM, Peter Eisentraut
> <peter(dot)eisentraut(at)2ndquadrant(dot)com
> <mailto:peter(dot)eisentraut(at)2ndquadrant(dot)com>> wrote:
>
> On 21.06.18 16:21, Don Seiler wrote:
> > -                                               (errmsg("connection
> > authorized: user=%s database=%s",
> > -                                                             
> >  port->user_name, port->database_name)));
> > +                                               (errmsg("connection
> > authorized: user=%s database=%s application=%s",
> > +                                                             
> >  port->user_name, port->database_name, port->application_name)));
>
> Why is it "application" and not "application_name"?
>
>
> I was trying to be consistent since we don't use "user_name" or
> "database_name" as labels even though those are the variable names.

"user" and "database" are the keys used in the startup packet.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2018-07-13 08:14:10 Re: Constraint documentation
Previous Message Amit Langote 2018-07-13 07:58:49 Re: How to make partitioning scale better for larger numbers of partitions