Re: Mention invalid null byte sequence

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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-08 10:34:15
Message-ID: 48125106de1a275b1e0c2d46b7c0a56a2b0675cb.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Mon, 2020-12-07 at 15:27 -0500, Tom Lane wrote:
> 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.

+1 on your patch.

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Tom Lane 2020-12-08 17:07:25 Re: Mention invalid null byte sequence
Previous Message PG Doc comments form 2020-12-08 08:13:18 Wrong configuration of tcp_user_timeout can terribly affects tcp_keepalives mechanism