| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | "David E(dot) Wheeler" <david(at)kineticode(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: extensible enum types |
| Date: | 2010-06-18 18:06:07 |
| Message-ID: | AANLkTinpnzqhQyMOBpXlODvhgy3P92TZAcSRh3BE-jTI@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jun 18, 2010 at 1:59 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> This was debated when we implemented enums. As between 1,2 and 4 there is
> often not much to choose, as alignment padding makes it pretty much the
> same. But any of them are more efficient than storing a numeric value or the
> label itself.
I was assuming the alternative was an integer, rather than a
numeric... but yeah, a numeric or the label itself would definitely
be larger.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2010-06-18 18:20:26 | Re: hstore ==> and deprecate => |
| Previous Message | Andrew Dunstan | 2010-06-18 17:59:09 | Re: extensible enum types |