| From: | John Naylor <john(dot)naylor(at)2ndquadrant(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PG 13 release notes, first draft |
| Date: | 2020-05-05 13:20:39 |
| Message-ID: | CACPNZCugECZv_5TNFFQ+R9Pp15PP5426oAstC1g7kTS1aLgrnw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Bruce, thanks for working on this again!
+<para>
+Allow UTF-8 escapes, e.g., E'\u####', in clients that don't use UTF-8
encoding (Tom Lane)
+</para>
I believe the term we want here is "Unicode escapes". This patch is
about the server encoding, which formerly needed to be utf-8 for
non-ascii characters. (I think the client encoding doesn't matter as
long as ascii bytes are represented.)
+<para>
+The UTF-8 characters must be available in the server encoding.
+</para>
Same here, s/UTF-8/Unicode/.
--
John Naylor https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dilip Kumar | 2020-05-05 13:43:47 | Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions |
| Previous Message | Benjamin Schaller | 2020-05-05 12:21:07 | Own index methods |