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

From Stephen Frost
Subject Re: [PATCH] Include application_name in "connection authorized" logmessage
Date
Msg-id 20180928002620.GZ4184@tamriel.snowman.net
Whole thread Raw
In response to Re: [PATCH] Include application_name in "connection authorized" logmessage  (Stephen Frost <sfrost@snowman.net>)
Responses Re: [PATCH] Include application_name in "connection authorized" logmessage  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
Greetings, all,

* Stephen Frost (sfrost@snowman.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.

Thanks!

Stephen

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [patch]overallocate memory for curly braces in array_out
Next
From: Gilles Darold
Date:
Subject: Re: Ora2Pg v19.1 has been released