Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1jYKL4-0006Ry-2u
	for pgsql-hackers@arkaria.postgresql.org; Tue, 12 May 2020 02:08:10 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1jYKL2-0003oN-UT
	for pgsql-hackers@arkaria.postgresql.org; Tue, 12 May 2020 02:08:08 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1jYKL2-0003oG-NY
	for pgsql-hackers@lists.postgresql.org; Tue, 12 May 2020 02:08:08 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1jYKL0-0001xp-Jt
	for pgsql-hackers@postgresql.org; Tue, 12 May 2020 02:08:07 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id 04C27N8w010923;
	Mon, 11 May 2020 22:07:23 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
cc: Chapman Flack <chap@anastigmatix.net>,
        John Naylor <john.naylor@2ndquadrant.com>,
        PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: PG 13 release notes, first draft
In-reply-to: <20200511230044.GB4666@momjian.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>
Comments: In-reply-to Bruce Momjian <bruce@momjian.us>
	message dated "Mon, 11 May 2020 19:00:44 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <10921.1589249243.1@sss.pgh.pa.us>
Date: Mon, 11 May 2020 22:07:23 -0400
Message-ID: <10922.1589249243@sss.pgh.pa.us>
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Precedence: bulk

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.

			regards, tom lane