From: Jeff Davis <pgsql@j-davis.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Doc: document bpchar, clarify relationship of text and varchar.
Date: Fri, 02 Dec 2022 12:18:22 -0800
Message-ID: <32a9b8357e8e29b04f395f92c53b64e015a4caf1.camel@j-davis.com> (raw)
In-Reply-To: <E1odZyZ-0000g2-AE@gemulon.postgresql.org>
References: <E1odZyZ-0000g2-AE@gemulon.postgresql.org>
On Wed, 2022-09-28 at 16:31 +0000, Tom Lane wrote:
> Doc: document bpchar, clarify relationship of text and varchar.
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?
I noticed this because there exists a hash function bug[1] that seems
to be visible with BPCHAR but not CHARACTER.
[1]
https://www.postgresql.org/message-id/7692740d4736e79032a5dac689cf2e304c03fa78.camel@j-davis.com
--
Jeff Davis
PostgreSQL Contributor Team - AWS
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: pgsql@j-davis.com, tgl@sss.pgh.pa.us, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Doc: document bpchar, clarify relationship of text and varchar.
In-Reply-To: <32a9b8357e8e29b04f395f92c53b64e015a4caf1.camel@j-davis.com>
* 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