Re: Decision by Monday: PQescapeString() vs. encoding violation - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Decision by Monday: PQescapeString() vs. encoding violation
Date
Msg-id yzs7j6ivvwhbxvg2bgwzv3ywy5yh5u5w2c6udygkcvk3jcqk5h@dikyjy5dyfev
Whole thread Raw
In response to Re: Decision by Monday: PQescapeString() vs. encoding violation  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Hi,

On 2025-02-15 15:52:01 -0500, Tom Lane wrote:
> The v5 patch seems Good Enough(TM) to me.

Agreed.


> We can refine it later perhaps; I don't think something like the above would
> affect anything that external code should care about.

I don't really think it's worth spending cycles on this anytime soon. It makes
sense to put the effort in to replace invalid "characters" in a minimal way
when intending to actually use the "stripped" output permanently. But all
we're trying to do here is to a) ensure that the backend will error out b)
reduce the chances that other tooling (psql, xml parsers, ..) get confused due
to invalidly encoded data.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Decision by Monday: PQescapeString() vs. encoding violation
Next
From: Andres Freund
Date:
Subject: Re: Decision by Monday: PQescapeString() vs. encoding violation