| From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
|---|---|
| To: | "'Hiroshi Inoue'" <Inoue(at)tpf(dot)co(dot)jp>, "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | AW: AW: ALTER TABLE DROP COLUMN |
| Date: | 2000-10-16 12:26:13 |
| Message-ID: | 11C1E6749A55D411A9670001FA6879633680A8@sdexcsrv1.f000.d0188.sd.spardat.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> This style of "DROP COLUMN" would change the attribute
> numbers whose positons are after the dropped column.
> Unfortunately we have no mechanism to invalidate/remove
> objects(or prepared plans) which uses such attribute numbers.
> And I've seen no proposal/discussion to solve this problem
> for DROP COLUMN feature. We wound't be able to prevent
> PostgreSQL from doing the wrong thing silently.
That issue got me confused now (There was a previous mail where
you suggested using logical colid most of the time). Why not use the
physical colid in prepared objects/plans. Since those can't currently change
it seems such plans would not be invalidated.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zeugswetter Andreas SB | 2000-10-16 12:45:14 | AW: analyze.c |
| Previous Message | Zeugswetter Andreas SB | 2000-10-16 10:23:56 | AW: Backup, restore & pg_dump |