| From: | "Albe Laurenz" <all(at)adv(dot)magwien(dot)gv(dot)at> |
|---|---|
| To: | "Simon Riggs *EXTERN*" <simon(at)2ndquadrant(dot)com> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Simple Column reordering |
| Date: | 2007-02-23 09:51:14 |
| Message-ID: | AFCCBB403D7E7A4581E48F20AF3E5DB201598183@EXADV1.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
How about INSERTs without column names? Wouldn't that also cease to
work?
In particular, 'pg_dump --format=plain --inserts' would produce unusable
output unless --attribute-inserts is also given, right?
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Smet | 2007-02-23 10:00:41 | Re: Simple Column reordering |
| Previous Message | Peter Eisentraut | 2007-02-23 09:37:19 | Re: pgsql: Change $(CC) to $(COMPILER) on Solaris gcc so -m64 is passed into |