column ordering, was Re: [PATCHES] Enums patch v2 - Mailing list pgsql-hackers

From Andrew Dunstan
Subject column ordering, was Re: [PATCHES] Enums patch v2
Date
Msg-id 458809D9.5030109@dunslane.net
Whole thread Raw
In response to Re: [PATCHES] Enums patch v2  (Gregory Stark <stark@enterprisedb.com>)
Responses Re: column ordering, was Re: [PATCHES] Enums patch v2
List pgsql-hackers
Gregory Stark wrote:
> "Andrew Dunstan" <andrew@dunslane.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


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: pg_restore fails with a custom backup file
Next
From: "Zeugswetter Andreas ADI SD"
Date:
Subject: Re: pg_restore fails with a custom backup file