column ordering, was Re: [PATCHES] Enums patch v2

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: column ordering, was Re: [PATCHES] Enums patch v2
Date: 2006-12-19 15:48:41
Message-ID: 458809D9.5030109@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Gregory Stark wrote:
> "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.
>
>

Sure, but the only sane way I can think of to do that would be have
separate logical and physical orderings, with a map between the two. I
guess we'd need to see what the potential space savings would be and
establish what the processing overhead would be, before considering it.
One side advantage would be that it would allow us to do the often
requested "add column at position x".

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zeugswetter Andreas ADI SD 2006-12-19 15:58:22 Re: pg_restore fails with a custom backup file
Previous Message Richard Huxton 2006-12-19 15:46:23 Re: Second attempt, roll your own autovacuum

Browse pgsql-patches by date

  From Date Subject
Next Message Martijn van Oosterhout 2006-12-19 16:25:04 Re: column ordering, was Re: [PATCHES] Enums patch v2
Previous Message Gregory Stark 2006-12-19 15:22:13 Re: [HACKERS] Enums patch v2