From: Tom Lane <tgl@sss.pgh.pa.us>
To: Laurenz Albe <laurenz.albe@cybertec.at>
cc: bugs-postgresql@antipoul.fr, pgsql-docs@lists.postgresql.org
Subject: Re: Mention invalid null byte sequence
In-reply-to: <48125106de1a275b1e0c2d46b7c0a56a2b0675cb.camel@cybertec.at>
References: <160720552914.710.16625261471128631268@wrigleys.postgresql.org>
 <0f0470f6d8c543793d2b71913cb230daea1aef3a.camel@cybertec.at>
 <3153759.1607372842@sss.pgh.pa.us>
 <48125106de1a275b1e0c2d46b7c0a56a2b0675cb.camel@cybertec.at>
Comments: In-reply-to Laurenz Albe <laurenz.albe@cybertec.at>
	message dated "Tue, 08 Dec 2020 11:34:15 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3256722.1607447245.1@sss.pgh.pa.us>
Date: Tue, 08 Dec 2020 12:07:25 -0500
Message-ID: <3256723.1607447245@sss.pgh.pa.us>
Precedence: bulk

Laurenz Albe <laurenz.albe@cybertec.at> writes:
> On Mon, 2020-12-07 at 15:27 -0500, Tom Lane wrote:
>> I agree with the submitter that the place one would expect to read about
>> this is in datatype-character.html.  So I'd propose the attached.
>> Maybe there's reason to repeat the info in charset.sgml, but it seems
>> like more of a datatype limitation than a character set issue.

> +1 on your patch.

Pushed, thanks for looking it over.

			regards, tom lane