Re: Invalid Unicode escape value at or near "\u0000" - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Invalid Unicode escape value at or near "\u0000"
Date
Msg-id 874e7e1d-0f8c-0a44-f030-494212317124@enterprisedb.com
Whole thread Raw
In response to Re: Invalid Unicode escape value at or near "\u0000"  (Thomas Munro <thomas.munro@gmail.com>)
List 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.



pgsql-hackers by date:

Previous
From: Greg Nancarrow
Date:
Subject: Re: Skipping logical replication transactions on subscriber side
Next
From: Peter Eisentraut
Date:
Subject: Re: Logical Replication - improve error message while adding tables to the publication in check_publication_add_relation