From: | Gregory Stark <stark(at)enterprisedb(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 15:22:13 |
Message-ID: | 87psafkj16.fsf@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
"Andrew Dunstan" <andrew(at)dunslane(dot)net> writes:
> I'm not a big fan of ordering columns to optimise record layout, except in the
> most extreme cases (massive DW type apps). I think visible column order should
> be logical, not governed by physical considerations.
Well as long as we're talking "should"s the database should take care of this
for you anyways.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Zeugswetter Andreas ADI SD | 2006-12-19 15:25:18 | Re: pg_restore fails with a custom backup file |
Previous Message | Tom Lane | 2006-12-19 15:19:34 | Re: [HACKERS] Enums patch v2 |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2006-12-19 15:48:41 | column ordering, was Re: [PATCHES] Enums patch v2 |
Previous Message | Tom Lane | 2006-12-19 15:19:34 | Re: [HACKERS] Enums patch v2 |