From: Tom Lane <tgl@sss.pgh.pa.us>
To: Brett Okken <brett.okken.os@gmail.com>
cc: pgsql-docs@lists.postgresql.org, Dave Cramer <davecramer@gmail.com>
Subject: Re: char 0x00
In-reply-to: 
 <CANBJVOH31rJxU=6wYULRyRVg6QfbgWRrFPrxUw1Ss20CR+rcBQ@mail.gmail.com>
References: 
 <CANBJVOH31rJxU=6wYULRyRVg6QfbgWRrFPrxUw1Ss20CR+rcBQ@mail.gmail.com>
Comments: In-reply-to Brett Okken <brett.okken.os@gmail.com>
	message dated "Thu, 26 Mar 2020 06:34:24 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <11840.1585232526.1@sss.pgh.pa.us>
Date: Thu, 26 Mar 2020 10:22:06 -0400
Message-ID: <11841.1585232526@sss.pgh.pa.us>
Precedence: bulk

Brett Okken <brett.okken.os@gmail.com> writes:
> It might also be helpful to state in the opening paragraph about character
> set support that the NUL character is not supported in any character set
> (except SQL_ASCII).

Uh, it's not supported *anywhere*, period.  If you managed to get the
server to accept a text string with an embedded NUL, I'd like to know
how exactly, because that's a missed validation.

As far as documentation goes, I'd be inclined to address the point
in the page about string data types,

https://www.postgresql.org/docs/current/datatype-character.html

with text along the lines of "The contents of a string value must be
validly encoded according to the database's encoding, and cannot include
the character with code zero".  I'd sort of thought we said that there
already, but I don't see it.

			regards, tom lane