Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Re: ALTER TABLE DROP COLUMN

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: The Hermit Hacker <scrappy(at)hub(dot)org>
Cc: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, 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 03:52:30
Message-ID: 200002280352.WAA16870@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
> > I would also change attname to '*already dropped %d' for
> > examle to avoid duplicate attname. 
> 
> 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?

And I think the problem was that there was too much code to modify to
allow this.

-- 
  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

In response to

Responses

pgsql-hackers by date

Next:From: Hiroshi InoueDate: 2000-02-28 04:25:06
Subject: RE: [HACKERS] Re: ALTER TABLE DROP COLUMN
Previous:From: The Hermit HackerDate: 2000-02-28 03:40:11
Subject: RE: [HACKERS] Re: ALTER TABLE DROP COLUMN

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group