| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Japin Li <japinli(at)hotmail(dot)com> |
| Cc: | "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Invalid Unicode escape value at or near "\u0000" |
| Date: | 2021-11-15 08:06:34 |
| Message-ID: | 874e7e1d-0f8c-0a44-f030-494212317124@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 13.11.21 06:40, Thomas Munro wrote:
> Yes, it is a valid codepoint, but unfortunately PostgreSQL can't
> support it because it sometimes deals in null terminated string, even
> though internally it does track string data and length separately. We
> have to do that to use libc facilities like strcoll_r(), and probably
> many other things.
By the way, I think the server-side issues around this are fixable. The
real problem in my mind is how to present such values in client APIs
such as libpq.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2021-11-15 08:15:39 | Re: Logical Replication - improve error message while adding tables to the publication in check_publication_add_relation |
| Previous Message | Greg Nancarrow | 2021-11-15 07:49:05 | Re: Skipping logical replication transactions on subscriber side |