From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
Cc: | John McCawley <nospam(at)hardgeus(dot)com>, Berend Tober <btober(at)seaworthysys(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Reordering columns in a table |
Date: | 2006-01-06 20:56:57 |
Message-ID: | 22770.1136581017@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-general |
"Jim C. Nasby" <jnasby(at)pervasive(dot)com> writes:
> Actually, I'm pretty sure this is on the TODO.
[ checks... ] No, it isn't. My recollection is that we looked very
hard at this around the time DROP COLUMN was implemented, and concluded
that we weren't ever going to support it, because distinguishing
physical from logical column numbers would create a nigh-inexhaustible
source of bugs. See the pghackers archives for lots of discussion.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Ribe | 2006-01-06 21:28:15 | Re: Reordering columns in a table |
Previous Message | Tom Lane | 2006-01-06 20:14:31 | Re: BUG #2144: Domain NOT NULL constraints ignored in rules |
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Harrison | 2006-01-06 21:09:37 | why am I getting a seq scan on this query? |
Previous Message | Tom Lane | 2006-01-06 20:47:33 | Re: ./configure --with-openssl=path fails |