| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> |
| Cc: | "Don Baccus" <dhogaza(at)pacifier(dot)com>, "Zeugswetter Andreas SB" <ZeugswetterA(at)wien(dot)spardat(dot)at>, "The Hermit Hacker" <scrappy(at)hub(dot)org>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "PostgreSQL Development" <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: AW: ALTER TABLE DROP COLUMN |
| Date: | 2000-10-15 15:57:32 |
| Message-ID: | 4908.971625452@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> writes:
> My trial implementation using physical/logical attribute numbers
> isn't so clean as I expected. I'm inclined to restrict my change to
> fix the TODO
> * ALTER TABLE ADD COLUMN to inherited table put column in wrong place
> though it would also introduce a backward compatibility.
I'm confused --- how will that make things any simpler or cleaner?
You still need physical/logical column numbering distinction in order
to fix inherited ADD COLUMN, don't you?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2000-10-15 17:16:32 | Re: select oid .... for update .... |
| Previous Message | KuroiNeko | 2000-10-15 15:10:08 | select oid .... for update .... |