Re: BPCHAR description in 8.3. Character Types is misleading and incomplete

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Sergei Katkovsky <skatkovsky(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: BPCHAR description in 8.3. Character Types is misleading and incomplete
Date: 2025-10-23 05:02:21
Message-ID: eec482cfac046c520929157d05d99d6c9694e1ce.camel@cybertec.at
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Mon, 2025-10-20 at 16:22 +0200, Laurenz Albe wrote:
> > Looks like nobody is against "insignificant/ignorable trailing
> > whitespace" or anything like that anymore? Am I right?
>
> Any verbal description will never completely represent the facts.
> But I'd say that "ignores trailing blanks" (not tabs, for example)
> is a fairly accurate description.

Here is a patch along these lines.

Yours,
Laurenz Albe

Attachment Content-Type Size
v1-0001-Improve-doc-for-bpchar-without-length-limit.patch text/x-patch 1.6 KB

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Shinya Kato 2025-10-23 05:58:37 Re: docs: Link to the correct protocol version inspection function
Previous Message Jelte Fennema-Nio 2025-10-22 09:42:07 docs: Link to the correct protocol version inspection function