| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net>, Don Seiler <don(at)seiler(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [PATCH] Include application_name in "connection authorized" log message |
| Date: | 2018-09-27 21:15:13 |
| Message-ID: | 757310d9-f742-bdc9-6900-ae817335f43b@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 24/09/2018 23:10, Stephen Frost wrote:
> Since we're putting it into common/string.c (which seems pretty
> reasonable to me, at least), I went ahead and changed it to be
> 'pg_clean_ascii'. I didn't see any other obvious cases where we could
> use this function (though typecmds.c does have an interesting ASCII
> check for type categories..).
I think we might want to contain this functionality to guc.c. In
general, we should allow more non-ASCII things rather than encourage
more "ASCII cleaning".
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2018-09-27 21:19:26 | Re: Collation versioning |
| Previous Message | Peter Eisentraut | 2018-09-27 21:10:08 | Re: file cloning in pg_upgrade and CREATE DATABASE |