pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <bruce@momjian.us>
To: Alvaro Herrera <alvherre@commandprompt.com>
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: Mon, 5 Sep 2011 14:21:46 -0400 (EDT)
Message-ID: <201109051821.p85ILkQ01814@momjian.us> (raw)
In-Reply-To: <1299856725-sup-5827@alvh.no-ip.org>

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 <type>"char"</type>, not <type>char</type>.
> > > 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  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +



view thread (20+ messages)  latest in thread

Message-ID: <201109051821.p85ILkQ01814@momjian.us>
Permalink:  ../201109051821.p85ILkQ01814@momjian.us/
Also on:    postgresql.org/message-id/201109051821.p85ILkQ01814@momjian.us

 · 

reply

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: bruce@momjian.us, alvherre@commandprompt.com, kevin.grittner@wicourts.gov, thom@linux.com, pgsql-hackers@postgresql.org
  Subject: Re: Couple document fixes
  In-Reply-To: <201109051821.p85ILkQ01814@momjian.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