elein <elein@sbcglobal.net> writes:
> I think I do not know the background on this.
I think it's mostly historical. The one-byte "char" datatype seems to
date back to Berkeley days, long before there was any concern for SQL
compliance (it's there in Postgres 4.2). "bpchar" was apparently added
in Postgres95 in order to provide SQL-like functionality --- but they
didn't pay any attention to duplicating the SQL name for it. The
keyword CHARACTER was added later, translating it to the internal name
bpchar in the parser. Eventually the keyword CHAR was added too, and
translated.
The real question at this point is what would break if we renamed "char"
to "char1". Since it's used extensively in the system catalogs, I'm
sure there would be some unhappiness involved. I am dubious that
merely avoiding confusion is a sufficient reason to change.
regards, tom lane
