| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Don Baccus <dhogaza(at)pacifier(dot)com> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [HACKERS] Happy column dropping |
| Date: | 2000-01-25 02:48:46 |
| Message-ID: | 200001250248.VAA21476@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> I was unaware that other folks had pointed to the copy/rename approach
> earlier as being a possible means of implementation. I thought you'd
> pulled that one out of your hat. Still, more advance discussion would've
> perhaps led to other approaches to investigate, just as discussion
> now is doing.
>
> I'm going to be blunt: implementation of "drop column" by doing a copy/rename
> isn't something one expects of a competitive commercial-quality RDBMS.
>
> Perhaps it's the best we can expect of Postgres, though. If so, so be it.
Maybe that is true. Having phantom column all over the code is going to
be a mess, and hardly worth it considering how many developers there are
and how many _big_ items still have to be done.
Messing up code for one feature is rarely worth it.
--
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 | Chris Bitmead | 2000-01-25 02:50:30 | Re: [HACKERS] Happy column dropping |
| Previous Message | Don Baccus | 2000-01-25 02:41:37 | Re: [HACKERS] Happy column dropping |