| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Chapman Flack <chap(at)anastigmatix(dot)net>, John Naylor <john(dot)naylor(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PG 13 release notes, first draft |
| Date: | 2020-05-12 02:48:17 |
| Message-ID: | 20200512024816.GW4666@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, May 11, 2020 at 10:07:23PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > I like your wording, but the "that encoding" wasn't clear enough for me,
> > so I reworded it to:
>
> > Allow Unicode escapes, e.g., E'\u####', U&'\####', to represent any
> > character available in the database encoding, even when the database
> > encoding is not UTF-8 (Tom Lane)
>
> How about "to be used for" instead of "to represent"? "Represent" kind
> of sounds like we're using these on output, which we aren't.
Uh, I think "used for" is worse though, since we are not using it. I
don't get the "output" feel of the word at all.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-05-12 02:48:23 | Re: No core file generated after PostgresNode->start |
| Previous Message | Bruce Momjian | 2020-05-12 02:46:14 | Re: PG 13 release notes, first draft |