From: Tom Lane <tgl@sss.pgh.pa.us>
To: David Fetter <david@fetter.org>
Cc: 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: Tue, 06 Sep 2011 11:19:45 -0400
Message-ID: <7024.1315322385@sss.pgh.pa.us> (raw)
In-Reply-To: <20110906042218.GM3924@fetter.org>
References: <20110905232916.GK3924@fetter.org>
<201109052333.p85NX9F26135@momjian.us>
<20110906000509.GL3924@fetter.org>
<1315271205-sup-7449@alvh.no-ip.org>
<20110906042218.GM3924@fetter.org>
David Fetter <david@fetter.org> writes:
> On Mon, Sep 05, 2011 at 10:07:29PM -0300, Alvaro Herrera wrote:
>> What would be the point?
> Removing the legacy "char" type, per original post. :)
Removing it is the wrong solution.
The idea of renaming it to char1 might be an appropriate balance of pain
versus benefit. Or perhaps not; I'd want to see a proposed patch before
committing to doing anything here.
> We've made changes as big on aesthetic grounds before, and if the
> change results in an enum type optimized for space efficiency, that's
> all to the good.
That's a pipe dream. You can't use enums in catalogs that underlie the
enum implementation. Possibly you could kluge something so that there
are phony entries in pg_enum reflecting the hard-wired values that the C
code uses, but I entirely fail to see any point in such a thing.
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, david@fetter.org, 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: <7024.1315322385@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