Re: [PGdocs] fix description for handling pf non-ASCII characters

Peter Smith <smithpb2250@gmail.com>

From: Peter Smith <smithpb2250@gmail.com>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: "Karl O. Pinc" <kop@karlpinc.com>, "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>, jian he <jian.universality@gmail.com>, Postgres hackers <pgsql-hackers@lists.postgresql.org>

Date: 2023-09-28T01:41:26Z

Lists: pgsql-hackers

On Thu, Sep 28, 2023 at 11:19 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> ... trailing bytes that could be mistaken for ASCII are precisely
> the property that causes us to reject an encoding as not backend-safe.

Oh, that is good to know. Thanks for the information.

======
Kind Regards,
Peter Smith.
Fujitsu Australia

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

doc: Fix descriptions related to the handling of non-ASCII characters
- 950e236e5069 16.1 landed
- 3ef18a90bdea 17.0 landed
pg_clean_ascii(): escape bytes rather than lose them
- 45b1a67a0fcb 16.0 cited
Make locale option behavior more consistent
- da5d4ea5aaac 16.0 cited