Re: Enums again

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Kaare Rasmussen <kar(at)kakidata(dot)dk>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Enums again
Date: 2005-11-08 14:01:26
Message-ID: 20051108140126.GB26953@surnet.cl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan wrote:

> In the catalog, pg_type would
> get a new column of type text[] that would hold the list of values, and
> typtype would have a new possible value of 'e' for enumeration. There
> might be other consequential changes too, but I think that would be most
> of it.

Huh, why not have the actual values in a separate catalog like
pg_enumvalues or some such?

> The only functions that actually need to have any knowledge of
> the enumeration strings are the input/output functions and the to/from
> text casts. These would get the relevant info from fcinfo.flinfo ... and
> then looking up the type cache - not sure yet if an extra cache
> operation is needed.

It'd be interesting to measure the difference of having the cache vs.
not having it.

Thinking on how to pg_dump the whole thing is important too.

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Creager 2005-11-08 14:11:39 Re: SIGSEGV taken on 8.1 during dump/reload
Previous Message Alvaro Herrera 2005-11-08 13:56:26 Re: plperl error when making 8.2dev CVS