Postgres Pro
Downloads
Home   >   mailing lists

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

From Don Seiler
Subject Re: [PATCH] Include application_name in "connection authorized" log message
Date
Msg-id CAHJZqBCCKutpAnXoo2Gj-w3WROBzyr9XmPiMDSmZ7qvAYNP+6g@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Include application_name in "connection authorized" logmessage  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: [PATCH] Include application_name in "connection authorized" logmessage  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
Tree view
On Mon, Jul 2, 2018 at 2:13 AM, Peter Eisentraut <peter.eisentraut@2ndquadrant.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.

 
--
Don Seiler
www.seiler.us

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: branches_of_interest.txt
Next
From: Fabrízio de Royes Mello
Date:
Subject: Re: psql \df option for procedures