From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jeff Davis <pgsql@j-davis.com>
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Doc: document bpchar, clarify relationship of text and varchar.
Date: Fri, 02 Dec 2022 15:26:46 -0500
Message-ID: <2129300.1670012806@sss.pgh.pa.us> (raw)
In-Reply-To: <32a9b8357e8e29b04f395f92c53b64e015a4caf1.camel@j-davis.com>
References: <E1odZyZ-0000g2-AE@gemulon.postgresql.org>
<32a9b8357e8e29b04f395f92c53b64e015a4caf1.camel@j-davis.com>
Jeff Davis <pgsql@j-davis.com> writes:
> BPCHAR is documented as an alias to CHARACTER, but the former can end
> up with no typmod at all whereas the latter defaults to CHARACTER(1).
> Should we document the case of using BPCHAR with no length?
Perhaps; you got specific wording in mind?
(I think that that difference is in fact documented somewhere,
but maybe not where you looked.)
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us, pgsql@j-davis.com, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Doc: document bpchar, clarify relationship of text and varchar.
In-Reply-To: <2129300.1670012806@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox