| From: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
|---|---|
| To: | Dave Cramer <pg(at)fastcrypt(dot)com> |
| Cc: | Hannu Krosing <hannu(at)tm(dot)ee>, Rod Taylor <pg(at)rbt(dot)ca>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: ALTER TABLE modifications |
| Date: | 2003-11-14 14:17:32 |
| Message-ID: | 20031114141732.GB23845@dcc.uchile.cl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On Fri, Nov 14, 2003 at 08:59:05AM -0500, Dave Cramer wrote:
> 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.
This is expected. Doing otherwise would incur into a much bigger
performance hit.
Anyway, IMHO no code should use SELECT * in any case, which is the only
scenario where one would expect physical column order to matter, isn't
it?
--
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"La primera ley de las demostraciones en vivo es: no trate de usar el sistema.
Escriba un guión que no toque nada para no causar daños." (Jakob Nielsen)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2003-11-14 14:23:17 | Re: ALTER TABLE modifications |
| Previous Message | Christopher Browne | 2003-11-14 14:13:48 | Re: Help with count(*) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2003-11-14 14:23:17 | Re: ALTER TABLE modifications |
| Previous Message | Dave Cramer | 2003-11-14 13:59:05 | Re: ALTER TABLE modifications |