From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: Kevin Grittner <kevin.grittner@wicourts.gov>
Cc: Thom Brown <thom@linux.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Couple document fixes
Date: Fri, 11 Mar 2011 11:01:06 -0500
Message-ID: <19827.1299859266@sss.pgh.pa.us> (raw)
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>
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
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-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, alvherre@commandprompt.com, bruce@momjian.us, kevin.grittner@wicourts.gov, thom@linux.com, pgsql-hackers@postgresql.org
Subject: Re: Couple document fixes
In-Reply-To: <19827.1299859266@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