From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: ALTER TABLE DROP COLUMN |
Date: | 2000-06-10 16:15:11 |
Message-ID: | 200006101615.MAA27967@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > -----Original Message-----
> > From: pgsql-hackers-owner(at)hub(dot)org
> > [mailto:pgsql-hackers-owner(at)hub(dot)org]On Behalf Of Bruce Momjian
> >
> > Seems we have 4 DROP COLUMN ideas:
> >
> > Method Advantage
> > -----------------------------------------------------------------
> > 1 invisible column marked by negative attnum fast
> > 2 invisible column marked by is_dropped column fast
> > 3 make copy of table without column col removed
> > 4 make new tuples in existing table without column col removed
> >
> > Folks, we had better choose one and get started.
> >
> > Number 1 Hiroshi has ifdef'ed out in the code. Items 1 and 2 have
> > problems with backend code and 3rd party code not seeing the dropped
> > columns,
>
> Hmm,doesn't *not seeing* mean the column is dropped ?
I meant problems of backend code and 3rd party code _seeing_ the dropped
column in pg_attribute.
--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2000-06-10 17:37:53 | Re: Current initdb broken. |
Previous Message | Peter Eisentraut | 2000-06-10 15:39:41 | Re: Current initdb broken. |