On 2018-06-22 12:16:18 -0400, Robert Haas wrote: > On Fri, Jun 22, 2018 at 11:17 AM, Stephen Frost <sfr...@snowman.net> wrote: > > The issue here is exactly that at the point where we emit the > > 'connection authorized' message, we haven't processed generic GUCs from > > the startup packet yet and therefore application_name isn't set as a > > GUC and, as a result, isn't included in the 'connection authorized' > > message, even if it's specified in log_line_prefix. > > > > There's no way, today, to get the application name included in the > > 'connection authorized' message, which certainly seems unfortunate and a > > bit surprising, hence this patch to fix that. > > 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. Greetings, Andres Freund
