From: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Simple Column reordering |
Date: | 2007-02-23 15:50:00 |
Message-ID: | 20070223155000.GH19527@nasby.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Feb 23, 2007 at 02:09:55PM +0000, Simon Riggs wrote:
> > If you really want an interim solution, what about a builtin function
> > that would explicitly mutate the definition and table contents (if any)
> > along the lines you want? (assuming that's lots less work than just
> > doing the whole thing right to start with). Or even one which just
> > *displayed* the optimal order might be sufficient assistance to DBAs who
> > want to take advantage of this.
>
> I think the only interim solution now is to put functionality into
> PgAdmin et al to optimize the column order.
Well, if it comes to that it would be good to have pgAdmin et all driven
by logic in the database, so that people using psql can benefit as well.
Perhaps a function that is passed an existing table and re-creates it in
optimal order (if it's empty...). Or at least spits out a CREATE TABLE
statement for you that's in optimal order.
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2007-02-23 16:04:14 | Re: Simple Column reordering |
Previous Message | Alvaro Herrera | 2007-02-23 15:43:08 | osprey dumped core on 8.2 |