From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, Tom Dunstan <pgsql(at)tomd(dot)cc>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: [HACKERS] Enums patch v2 |
Date: | 2006-12-19 14:58:48 |
Message-ID: | 20061219145848.GK27098@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Andrew Dunstan wrote:
> As for efficiency, I agree with what Tom says about alignment and
> padding dissolving away any perceived advantage in most cases. If we
> ever get around to optimising record layout we could revisit it.
I don't, because there are always those that are knowledgeable enough to
know how to reduce space lost to padding. So it would be nice to have
2-byte enums on-disk, and resolve them based on the column's typid. But
then, I'm not familiar with the patch at all so I'm not sure if it's
possible.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2006-12-19 15:07:55 | Re: pg_restore fails with a custom backup file |
Previous Message | Hans-Juergen Schoenig | 2006-12-19 14:56:01 | Re: Core dump in PL/pgSQL ... |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2006-12-19 15:11:42 | Re: [HACKERS] Enums patch v2 |
Previous Message | Bruce Momjian | 2006-12-19 14:45:38 | Re: Updated XML patch |