Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 5882AB5DF62 for ; Mon, 5 Sep 2011 15:25:19 -0300 (ADT) 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 29048-01-6 for ; Mon, 5 Sep 2011 18:25:12 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from momjian.us (momjian.us [70.90.9.53]) by mail.postgresql.org (Postfix) with ESMTP id 7D383B5F46C for ; Mon, 5 Sep 2011 15:21:55 -0300 (ADT) Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id p85ILkQ01814; Mon, 5 Sep 2011 14:21:46 -0400 (EDT) From: Bruce Momjian Message-Id: <201109051821.p85ILkQ01814@momjian.us> Subject: Re: Couple document fixes In-Reply-To: <1299856725-sup-5827@alvh.no-ip.org> To: Alvaro Herrera Date: Mon, 5 Sep 2011 14:21:46 -0400 (EDT) CC: Kevin Grittner , Thom Brown , PostgreSQL-development X-Mailer: ELM [version 2.4ME+ PL124 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.404 tagged_above=-5 required=5 tests=BAYES_00=-1.9, RP_MATCHES_RCVD=-0.504 X-Spam-Level: X-Archive-Number: 201109/178 X-Sequence-Number: 194367 Alvaro Herrera wrote: > Removing CC to pg-docs so that Robert reads it. > > Excerpts from Bruce Momjian's message of vie mar 11 08:13:20 -0300 2011: > > Kevin Grittner wrote: > > > > relpersistence should be "char", not char. > > > Oddly enough, there is a difference. > > > > I am unsure on that one. We have many 'char' mentions in catalog.sgml, > > and I don't see any of them shown as '"char"'. (Wow, we should have > > just called this type char1, but I think that name came from Berkeley!) > > The big problem is that the pg_type name is really "char" _without_ > > quotes. > > 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. > > Discussed the idea a bit on IM with Bruce, but couldn't find any really > good alternative. Idea floated so far: > > * byte (seems pretty decent to me) > * octet (though maybe people would expect it'd output as a number) > * char1 (looks ugly, but then we have int4 and so on) > * achar (this one is just plain weird) > > None seems great. Thoughts? Any new ideas on how to document our "char" data type? -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +