Subject: Re: PG 13 release notes, first draft
To: Bruce Momjian <bruce@momjian.us>, Tom Lane <tgl@sss.pgh.pa.us>
References: <20200505031600.GB21752@momjian.us>
 <CACPNZCugECZv_5TNFFQ+R9Pp15PP5426oAstC1g7kTS1aLgrnw@mail.gmail.com>
 <20200505143118.GH21752@momjian.us> <5EB317A8.1020907@anastigmatix.net>
 <20200507134657.GK3649@momjian.us> <5EB44EBA.3040206@anastigmatix.net>
 <20200511230044.GB4666@momjian.us> <10922.1589249243@sss.pgh.pa.us>
 <20200512024816.GW4666@momjian.us>
Cc: John Naylor <john.naylor@2ndquadrant.com>,
 PostgreSQL-development <pgsql-hackers@postgresql.org>
From: Chapman Flack <chap@anastigmatix.net>
Message-ID: <5EBA1333.1080706@anastigmatix.net>
Date: Mon, 11 May 2020 23:08:35 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <20200512024816.GW4666@momjian.us>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 05/11/20 22:48, Bruce Momjian wrote:
> On Mon, May 11, 2020 at 10:07:23PM -0400, Tom Lane wrote:
>> Bruce Momjian <bruce@momjian.us> writes:
>>> 	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.

'specify' ?

-Chap