Michael Glaesemann <grzm@myrealbox.com> writes:
> On Apr 26, 2005, at 11:52, Keith Worthington wrote:
>> The type "char" (note the quotes) is different
>> from char(1)in that it only uses one byte of
>> storage. It is internally used in the system
>> catalogs as a poor-man's enumeration type.
>>
>> Is this a SQL standard data type?
> No.
Check.
>> Can I expect this type to be supported in PostgreSQL 'forever'?
> I'm not in a position to say, but I do know that "It is internally used
> in the system catalogs" and the system catalogs carry with them the
> explicit warning that they may change--and have changed in the
> past--between releases.
It's unlikely that we'd get rid of "char", simply because it'd be more
work to get rid of its uses in the system catalogs than it would be
worth. But bear in mind that we do feel free to whack around behaviors
that are not mandated by the SQL spec. As an example, there used to be
arithmetic operators (!) on the "char" type, but we got rid of them
because they caused great confusion.
If you use "char" columns only to store and retrieve single ASCII
characters, and don't expect any more operations on them than simple
comparisons, I think you'll be fine for the foreseeable future.
regards, tom lane
