Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 3CC371337B69 for ; Fri, 11 Mar 2011 12:09:12 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 41677-07 for ; Fri, 11 Mar 2011 16:09:04 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from spinlock.commandprompt.com (unknown [207.173.203.215]) by mail.postgresql.org (Postfix) with ESMTP id 30D6C1337B2F for ; Fri, 11 Mar 2011 12:09:04 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by spinlock.commandprompt.com (Postfix) with ESMTP id 31F2B348046; Fri, 11 Mar 2011 08:08:42 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at commandprompt.com Received: from spinlock.commandprompt.com ([127.0.0.1]) by localhost (spinlock.commandprompt.com.commandprompt.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GdvpPWbp2dkC; Fri, 11 Mar 2011 08:08:40 -0800 (PST) Received: from perhan.alvh.no-ip.org (unknown [190.95.20.220]) by spinlock.commandprompt.com (Postfix) with ESMTPSA id D2548348022; Fri, 11 Mar 2011 08:08:39 -0800 (PST) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id E30E46E58B; Fri, 11 Mar 2011 13:08:36 -0300 (CLST) Content-Type: text/plain; charset=UTF-8 Cc: Bruce Momjian , Kevin Grittner , Thom Brown , PostgreSQL-development Subject: Re: Couple document fixes From: Alvaro Herrera To: Tom Lane In-reply-to: <19827.1299859266@sss.pgh.pa.us> 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> <19827.1299859266@sss.pgh.pa.us> Date: Fri, 11 Mar 2011 13:08:36 -0300 Message-Id: <1299859616-sup-5570@alvh.no-ip.org> User-Agent: Sup/git Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.107 tagged_above=-5 required=5 tests=BAYES_00=-1.9, RDNS_NONE=0.793 X-Spam-Level: X-Archive-Number: 201103/794 X-Sequence-Number: 184044 Excerpts from Tom Lane's message of vie mar 11 13:01:06 -0300 2011: > Alvaro Herrera writes: > > Excerpts from Tom Lane's message of vie mar 11 12:40:50 -0300 2011: > >> Alvaro Herrera 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. Oh. Right, of course. Seems the only option is to continue living with it. (Well actually the other option would be to rename it and break backwards compatibility. I'm not sure anyone is going to be happy with that though.) -- Álvaro Herrera The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support