Re: PG 13 release notes, first draft

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(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:07:23
Message-ID: 10922.1589249243@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2020-05-12 02:16:53 Re: PG 13 release notes, first draft
Previous Message Kyotaro Horiguchi 2020-05-12 02:01:03 Re: pg13: xlogreader API adjust