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

From: Sergei Katkovsky <skatkovsky(at)gmail(dot)com>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
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-20 12:42:30
Message-ID: CAAf8JyKpZY+bWLmyP-hR+sQiR0yS+nDTrdqaQbWgrf6uxsXYoQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Sat, Oct 18, 2025 at 2:36 AM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:

> But perhaps it is really better to leave things as they are now, perhaps
> replacing "blank-trimming", perhaps as "variable-length string that ignores
> training blanks".

Looks like nobody is against "insignificant/ignorable trailing
whitespace" or anything like that anymore? Am I right?

With best regards,
Sergei Katkovskii

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Laurenz Albe 2025-10-20 14:22:50 Re: BPCHAR description in 8.3. Character Types is misleading and incomplete
Previous Message Laurenz Albe 2025-10-17 22:36:02 Re: BPCHAR description in 8.3. Character Types is misleading and incomplete