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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: skatkovsky(at)gmail(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-15 19:29:36
Message-ID: 1307875.1760556576@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-docs

Jeff Davis <pgsql(at)j-davis(dot)com> writes:
> Please take a look at the attached patch. If you'd like your name
> included in the commit, please send it as you'd like it to appear.

I don't understand why any of these variants are better than the
original wording "blank-padded". That has the non-negligible
advantage of corresponding to the type name, and furthermore
appears in many other places in our docs and source code.

There may be some other wording improvements we could make here,
but I think b69db5173 was fundamentally misguided in this respect.

regards, tom lane

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Jeff Davis 2025-10-15 20:09:54 Re: BPCHAR description in 8.3. Character Types is misleading and incomplete
Previous Message Alpha Shuro 2025-10-15 19:07:27 [DOCS] document ShareLock behaviour when using a deferred unique index