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

From: Don Seiler <don(at)seiler(dot)us>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: [PATCH] Include application_name in "connection authorized" log message
Date: 2018-09-28 23:59:07
Message-ID: CAHJZqBDykUjTR+4EW4yvqzOHof=zY=V6gxU4koxj9foBVEWj7Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thanks for all the guidance!

Don.

On Fri, Sep 28, 2018, 18:12 Stephen Frost <sfrost(at)snowman(dot)net> wrote:

> Greetings,
>
> * Stephen Frost (sfrost(at)snowman(dot)net) wrote:
> > * Stephen Frost (sfrost(at)snowman(dot)net) wrote:
> > > I still don't see that as a reason for tools to be suseptible to
> serious
> > > issues if a funky user gets created and I'd be surprised if there
> > > weren't other ways to get funky characters into the log file, but
> that's
> > > all ultimately an independent issue from this. I'll add the comments
> as
> > > discussed and discourage using the clean ascii function, but otherwise
> > > keep things as-is in that regard.
> >
> > Updated patch with lots of comments added around pg_clean_ascii() about
> > why it exists, why we do the cleaning, and warnings to discourage people
> > from using it without good cause. I've also done some additional
> > testing with it and it seems to be working well. I'll poke at it a bit
> > more tomorrow but if there aren't any other concerns, I'll commit it
> > towards the end of the day.
>
> Pushed, thanks all for the help and discussion, and thanks to Don for
> his patch!
>
> Thanks!
>
> Stephen
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2018-09-29 00:46:36 Re: executor relation handling
Previous Message Stephen Frost 2018-09-28 23:16:25 Re: Use durable_unlink for .ready and .done files for WAL segment removal