From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | bugs-postgresql(at)antipoul(dot)fr, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Mention invalid null byte sequence |
Date: | 2020-12-07 20:27:22 |
Message-ID: | 3153759.1607372842@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> writes:
> On Sat, 2020-12-05 at 21:58 +0000, PG Doc comments form wrote:
>> The following documentation comment has been logged on the website:
>> Page: https://www.postgresql.org/docs/13/datatype-character.html
>> Description:
>>
>> So it should written in the character type that null byte are not accepted,
>> it would make like easier to migrate to PostgreSQL :)
> +1; how about the attached patch?
I had thought that this was already documented, but after digging around
I can only find it mentioned in the contexts of saying that literal
strings and quoted identifiers can't contain \0. So yeah, we need to
improve that.
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.
regards, tom lane
Attachment | Content-Type | Size |
---|---|---|
document-that-you-cant-store-NUL.patch | text/x-diff | 1.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | PG Doc comments form | 2020-12-08 03:13:30 | pg_upgrade is not correct |
Previous Message | Adrien CLERC | 2020-12-07 09:57:47 | Re: Mention invalid null byte sequence |