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

Jeff Davis <pgsql@j-davis.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



pgsql-docs by date:

Previous
From: Alpha Shuro
Date:
Subject: [DOCS] document ShareLock behaviour when using a deferred unique index
Next
From: Jeff Davis
Date:
Subject: Re: BPCHAR description in 8.3. Character Types is misleading and incomplete