From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, 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 16:04:14 |
Message-ID: | 20070223160414.GD18066@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Jim C. Nasby wrote:
> 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.
That's just working around the fact that the engine is not smart enough
to do the right thing (semi-) automatically. We don't support that kind
of operation, just like we don't support optimizer hints.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2007-02-23 16:22:17 | Re: autovacuum next steps, take 2 |
Previous Message | Jim C. Nasby | 2007-02-23 15:50:00 | Re: Simple Column reordering |