Re: ALTER TABLE modifications - Mailing list pgsql-patches

From Rod Taylor
Subject Re: ALTER TABLE modifications
Date
Msg-id 1068820376.35839.15.camel@jester
Whole thread Raw
In response to Re: ALTER TABLE modifications  (Dave Cramer <pg@fastcrypt.com>)
Responses Re: ALTER TABLE modifications  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-patches
On Fri, 2003-11-14 at 08:59, Dave Cramer wrote:
> Rod,
>
> I tried the current patch on a RC2 release, and I noticed one
> undesirable side affect.
>
> Modifying a column  moves it to the end. In high availability situations
> this would not be desirable, I would imagine it would break lots of
> code.

Yes, I've done that to myself a few times.

The method is rename old column, add new column, move data across, move
or reform dependencies, drop old column.

Adding the new column puts it to the end. In order to avoid the
repositioning we would need some kind of a position abstraction from the
physical storage to what the user sees. It's on the TODO list, but not a
part of this patch.


pgsql-patches by date:

Previous
From: Hannu Krosing
Date:
Subject: Re: ALTER TABLE modifications
Next
From: Peter Eisentraut
Date:
Subject: Re: ALTER TABLE modifications