| From: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Chapman Flack <chap(at)anastigmatix(dot)net> |
| Subject: | Re: Unicode escapes with any backend encoding |
| Date: | 2020-01-14 01:44:16 |
| Message-ID: | CAA8=A781rCyH+iOwmOvsjpLc9B6FuWa8v-LnCUdtc0Y8KfTqHQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jan 14, 2020 at 10:02 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>
> Grepping for other direct uses of unicode_to_utf8(), I notice that
> there are a couple of places in the JSON code where we have a similar
> restriction that you can only write a Unicode escape in UTF8 server
> encoding. I'm not sure whether these same semantics could be
> applied there, so I didn't touch that.
>
Off the cuff I'd be inclined to say we should keep the text escape
rules the same. We've already extended the JSON standard y allowing
non-UTF8 encodings.
cheers
andrew
--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-01-14 02:05:34 | Re: Unicode escapes with any backend encoding |
| Previous Message | Tom Lane | 2020-01-14 01:38:17 | Re: BUG #16059: Tab-completion of filenames in COPY commands removes required quotes |