On Thu, 2007-02-22 at 23:49 -0300, Alvaro Herrera wrote: > Andrew Dunstan wrote: > > Simon Riggs wrote: > > > > > > I propose that at CREATE TABLE time, the column ordering is re-ordered > > > so that the table columns are packed more efficiently. This would be a > > > physical re-ordering, so that SELECT * and COPY without explicit column > > > definitions would differ from the original CREATE TABLE statement. > > > > > > This would be an optional feature, off by default, controlled by a > > > USERSET GUC > > > optimize_column_order = off (default) | on > > > > Umm, you want a GUC setting to enable standards-breaking behaviour and > > that will be obsolete when we do column ordering right, which is not > > likely to be more than one release away, and could even still happen in > > this coming release? > > Given that we already seem to have a patch implementing a complete > solution, or part thereof, this would seem a rather shortsighted > proposal. Why not develop the whole thing and be done with it?
That would be my preference, but if it doesn't happen, I wanted to have a clear secondary proposal documented. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
