Re: [PATCH] Include application_name in "connection authorized" logmessage
От | Peter Eisentraut |
---|---|
Тема | Re: [PATCH] Include application_name in "connection authorized" logmessage |
Дата | |
Msg-id | 30ecd2ed-e779-1e5e-5acd-0297a3367fc3@2ndquadrant.com обсуждение исходный текст |
Ответ на | Re: [PATCH] Include application_name in "connection authorized" log message (Don Seiler <don@seiler.us>) |
Ответы |
Re: [PATCH] Include application_name in "connection authorized" logmessage
|
Список | pgsql-hackers |
On 02.07.18 15:12, Don Seiler wrote: > On Mon, Jul 2, 2018 at 2:13 AM, Peter Eisentraut > <peter.eisentraut@2ndquadrant.com > <mailto: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. "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
В списке pgsql-hackers по дате отправления: