| From: | Don Baccus <dhogaza(at)pacifier(dot)com> |
|---|---|
| To: | The Hermit Hacker <scrappy(at)hub(dot)org>, Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | RE: [HACKERS] Re: ALTER TABLE DROP COLUMN |
| Date: | 2000-02-28 05:30:06 |
| Message-ID: | 3.0.1.32.20000227213006.00fc1750@mail.pacifier.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At 11:40 PM 2/27/00 -0400, The Hermit Hacker wrote:
>Okay, just curious here, but ... what you are proposing *sounds* to me
>like half-way to what started this thread. (*Please* correct me if I'm
>wrong) ...
>
>Essentially, in your proposal, when you drop a column, all subsequent
>tuples inserted/updated would have ... that one column missing? So,
>instead of doing a massive sweep through the table and removing that
>column, only do it when an insert/update happens?
>
>Basically, eliminate the requirement to re-write every tuples, only those
>that have activity?
Yes, this was one of the ideas that cropped up in previous discussion.
- Don Baccus, Portland OR <dhogaza(at)pacifier(dot)com>
Nature photos, on-line guides, Pacific Northwest
Rare Bird Alert Service and other goodies at
http://donb.photo.net.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | subaesh ramjan | 2000-02-28 05:54:09 | info |
| Previous Message | Don Baccus | 2000-02-28 05:26:30 | RE: [HACKERS] Re: ALTER TABLE DROP COLUMN |