pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@commandprompt.com>
To: 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 12:23:22 -0300
Message-ID: <1299856725-sup-5827@alvh.no-ip.org> (raw)
In-Reply-To: <201103111113.p2BBDKX04227@momjian.us>
References: <201103111113.p2BBDKX04227@momjian.us>

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?

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support



view thread (20+ messages)  latest in thread

Message-ID: <1299856725-sup-5827@alvh.no-ip.org>
Permalink:  ../1299856725-sup-5827@alvh.no-ip.org/
Also on:    postgresql.org/message-id/1299856725-sup-5827@alvh.no-ip.org

 · 

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: 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: <1299856725-sup-5827@alvh.no-ip.org>

* 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