From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Column storage positions |
Date: | 2007-02-21 20:55:31 |
Message-ID: | 45DCB1C3.1090700@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera wrote:
>>
>> I haven't understood Alvaro to suggest not keeping 3 numbers.
>>
>
> Right, I'm not advocating not doing that -- I'm just saying that the
> first step to that could be decoupling physical position with attr id
> :-) Logical column ordering (the order in which SELECT * expands to)
> seems to me to be a different feature.
>
>
Except in the sense that divorcing the id from the storage order makes
it possible to do sanely. :-)
Incidentally, I'm sure there would be a full scale revolt if there was a
suggestion to alter the visible behaviour of SELECT *, COPY and other
commands that rely on the logical ordering (which is currently, and
unless we provide commands to alter it would stay as, the definition
order). That's the order pg_dump should use IMNSHO - it should never
have to worry about the physical order nor about explicitly setting the
logical order.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory Stark | 2007-02-21 20:56:09 | Re: Status of Hierarchical Queries |
Previous Message | Gregory Stark | 2007-02-21 20:50:32 | Re: Column storage positions |