Re: BPCHAR description in 8.3. Character Types is misleading and incomplete - Mailing list pgsql-docs

From Sergei Katkovsky
Subject Re: BPCHAR description in 8.3. Character Types is misleading and incomplete
Date
Msg-id CAAf8JyKpZY+bWLmyP-hR+sQiR0yS+nDTrdqaQbWgrf6uxsXYoQ@mail.gmail.com
Whole thread Raw
In response to Re: BPCHAR description in 8.3. Character Types is misleading and incomplete  (Laurenz Albe <laurenz.albe@cybertec.at>)
Responses Re: BPCHAR description in 8.3. Character Types is misleading and incomplete
List pgsql-docs
On Sat, Oct 18, 2025 at 2:36 AM Laurenz Albe <laurenz.albe@cybertec.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



pgsql-docs by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: BPCHAR description in 8.3. Character Types is misleading and incomplete
Next
From: Laurenz Albe
Date:
Subject: Re: BPCHAR description in 8.3. Character Types is misleading and incomplete