From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | The Hermit Hacker <scrappy(at)hub(dot)org> |
Cc: | PostgreSQL-core <pgsql-core(at)postgresql(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ALTER TABLE DROP COLUMN |
Date: | 2000-10-10 00:05:19 |
Message-ID: | 200010100005.UAA29356@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > > > > I am not convinced that a 2x penalty for DROP COLUMN is such a huge
> > > > > problem that we should give up all the normal safety features of SQL
> > > > > in order to avoid it. Seems to me that DROP COLUMN is only a big issue
> > > > > during DB development, when you're usually working with relatively small
> > > > > amounts of test data anyway.
> > > > >
> > > >
> > > > Bingo!
> > >
> > > you are jumping on your 'I agree/Bingo' much much too fast :)
> >
> > You know this DROP COLUMN is a hot button for me.
>
> Ya, but in one email, you appear to agree with me ... then Tom posts a
> good point and you jump over to that side ... at least pick a side? :) I
> too wish to see it implemented, I just don't want to have to double my
> disk space if at some point I decide to upgrade an application and find
> out that they decided to change their schema(s) :(
Sorry, I liked the vacuum idea, but 2x disk usage, not 100 at a time.
--
Bruce Momjian | http://candle.pha.pa.us
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 | Tim Kientzle | 2000-10-10 00:06:37 | Re: [GENERAL] Using BLOBs with PostgreSQL |
Previous Message | The Hermit Hacker | 2000-10-10 00:02:46 | Re: ALTER TABLE DROP COLUMN |