From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Chapman Flack <chap(at)anastigmatix(dot)net> |
Cc: | John Naylor <john(dot)naylor(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: benchmarking Flex practices |
Date: | 2019-07-25 02:00:09 |
Message-ID: | 12800.1564020009@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Chapman Flack <chap(at)anastigmatix(dot)net> writes:
> On 07/24/19 03:45, John Naylor wrote:
>> On Sun, Jul 21, 2019 at 3:14 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> However, my second reaction was that maybe you were on to something
>>> upthread when you speculated about postponing de-escaping of
>>> Unicode literals into the grammar. If we did it like that then
> With the de-escaping postponed, I think we'd be able to move beyond the
> current odd situation where Unicode escapes can't describe non-ascii
> characters, in exactly and only the cases where you need them to.
How so? The grammar doesn't really have any more context information
than the lexer does. (In both cases, it would be ugly but not really
invalid for the transformation to depend on the database encoding,
I think.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2019-07-25 02:18:07 | Re: POC: Cleaning up orphaned files using undo logs |
Previous Message | Kyotaro Horiguchi | 2019-07-25 01:39:36 | Re: [HACKERS] WAL logging problem in 9.4.3? |