From: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com>, Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: logical column ordering |
Date: | 2015-02-27 20:43:15 |
Message-ID: | 54F0D6E3.5080309@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
OK, so let me summarize here (the other posts in this subthread are
discussing the user interface, not the use cases, so I'll respond here).
There are two main use cases:
1) change the order of columns in "SELECT *"
- display columns so that related ones grouped together
(irrespectedly whether they were added later, etc.)
- keep columns synced with COPY
- requires user interface (ALTER TABLE _ ALTER COLUMN _ SET ORDER _)
2) optimization of physical order (efficient storage / tuple deforming)
- more efficient order for storage (deforming)
- may be done manually by reordering columns in CREATE TABLE
- should be done automatically (no user interface required)
- seems useful both for on-disk physical tuples, and virtual tuples
Anything else?
--
Tomas Vondra http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2015-02-27 20:48:20 | Re: logical column ordering |
Previous Message | Josh Berkus | 2015-02-27 20:42:12 | Re: logical column ordering |