Re: Add column and specify the column position in a table

From: "Guillaume Lelarge" <guillaume(dot)lelarge(at)gmail(dot)com>
To: "Andrew Sullivan" <ajs(at)crankycanuck(dot)ca>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: Add column and specify the column position in a table
Date: 2006-05-18 16:54:46
Message-ID: d854adec0605180954t2f546e21u991832bca7469bef@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

2006/5/18, Andrew Sullivan <ajs(at)crankycanuck(dot)ca>:
> On Thu, May 18, 2006 at 05:43:19PM +0200, Guillaume Lelarge wrote:
> > Do you mean that, using "alter table test add column" with the "after"
> > option, MySQL creates a new table, populates it with the old table
> > data and finally drops the old table ? I mean, there's the same
> > performance problem with big tables ?
>
> MySQL does that for a great deal of its DDL. Yes, the performance is
> awful for this on big tables.
>
> The reason I didn't answer the OP's question, though, is that I can't
> think of a legitimate reason to do this anyway. The physical layout
> of the columns should not be of concern to the developer, who should
> be naming the columns anyway.
>

I totally agree on the physical layout. Just being curious :)

--
Guillaume.

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Tony Wasson 2006-05-18 17:53:58 Re: help..postgresql mulyiple return values
Previous Message Markus Schaber 2006-05-18 16:38:25 Re: Constraint question