To: Alvaro Herrera <alvherre@commandprompt.com>
cc: Bruce Momjian <bruce@momjian.us>,
	Kevin Grittner <kevin.grittner@wicourts.gov>, Thom Brown <thom@linux.com>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Couple document fixes 
In-reply-to: <1299858450-sup-6133@alvh.no-ip.org> 
References: <201103111113.p2BBDKX04227@momjian.us>
	<1299856725-sup-5827@alvh.no-ip.org>
	<19167.1299858050@sss.pgh.pa.us>
	<1299858450-sup-6133@alvh.no-ip.org>
Comments: In-reply-to Alvaro Herrera <alvherre@commandprompt.com>
	message dated "Fri, 11 Mar 2011 12:51:47 -0300"
Date: Fri, 11 Mar 2011 11:01:06 -0500
Message-ID: <19827.1299859266@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Alvaro Herrera <alvherre@commandprompt.com> writes:
> Excerpts from Tom Lane's message of vie mar 11 12:40:50 -0300 2011:
>> Alvaro Herrera <alvherre@commandprompt.com> writes:
>>> One idea is to rename the type to something else.  We could keep "char"
>>> as an alias for backwards compatibility, but use the new name in system
>>> catalogs, and document it as the main name of the type.

>> We don't have type aliases...

> I meant the conversion we do from a certain name (say because it's the
> SQL-mandated name for the type) to the internal name, such as mapping
> integer to int4.

That works for keywords.  "char" is, by definition, not a keyword.

			regards, tom lane