Re: PG 13 release notes, first draft - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: PG 13 release notes, first draft
Date
Msg-id 20200512024816.GW4666@momjian.us
Whole thread Raw
In response to Re: PG 13 release notes, first draft  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: PG 13 release notes, first draft  (Chapman Flack <chap@anastigmatix.net>)
List pgsql-hackers
On Mon, May 11, 2020 at 10:07:23PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce@momjian.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@momjian.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 +



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: PG 13 release notes, first draft
Next
From: Tom Lane
Date:
Subject: Re: No core file generated after PostgresNode->start